Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Total CMS

Content management system for modern websites

CategoryMarketing
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 24, 2026

Overview

Connect Total CMS with Flows360

Content management system for modern websites

Use the Total CMS connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 14 actions and 1 trigger.

Available actions

  • Get Content
  • Get Blog Post
  • Save Blog Post
  • Save Blog Post Gallery Image
  • Save Blog Post Image
  • Save Date Content
  • Save Depot
  • Save File
  • Plus 6 additional declared actions.

Available triggers

  • New Blog Post

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Total CMS
  • Package: @activepieces/piece-totalcms@0.2.0
  • Exact artifact digest: sha256:6afdc6fe59cd5f044524b0b6e1302f025cf931e791a05389ea709ce455d1bf63
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Content (get_content), Get content from your Total CMS website Classification: read.
  • Get Blog Post (get_blog_post), Get a blog post from Total CMS Classification: read.
  • Save Blog Post (save_blog_post), Save blog content to Total CMS Classification: read.
  • Save Blog Post Gallery Image (save_blog_gallery), Save image to Total CMS blog post gallery Classification: read.
  • Save Blog Post Image (save_blog_image), Save image to Total CMS blog post Classification: read.
  • Save Date Content (save_date), Save date content to Total CMS Classification: read.
  • Save Depot (save_depot), Save file to Total CMS depot Classification: read.
  • Save File (save_file), Save file to Total CMS Classification: read.
  • Save Gallery Image (save_gallery), Save image to Total CMS gallery Classification: read.
  • Save Image (save_image), Save image to Total CMS Classification: read.
  • Save Text Content (save_text), Save text content to Total CMS Classification: read.
  • Save Toggle (save_toggle), Save toggle content to Total CMS Classification: read.
  • Save Video Content (save_video), Save video content to Total CMS Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Blog Post, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects15
Supported actionsNot published
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Total CMS Domain Required
  • License Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Content Yes No Get content from your Total CMS website
Get Blog Post Yes No Get a blog post from Total CMS
Save Blog Post Yes No Save blog content to Total CMS
Save Blog Post Gallery Image Yes No Save image to Total CMS blog post gallery
Save Blog Post Image Yes No Save image to Total CMS blog post
Save Date Content Yes No Save date content to Total CMS
Save Depot Yes No Save file to Total CMS depot
Save File Yes No Save file to Total CMS
Save Gallery Image Yes No Save image to Total CMS gallery
Save Image Yes No Save image to Total CMS
Save Text Content Yes No Save text content to Total CMS
Save Toggle Yes No Save toggle content to Total CMS
Save Video Content Yes No Save video content to Total CMS
Custom API Call Yes No Make a custom API call to a specific endpoint
New Blog Post Yes No polling trigger declared by the pinned package.

Triggers

New Blog Post · Poll

Triggers when a new blog post is published

Inputs

  • slug · string

Setup

Setup

  1. Add the Total CMS connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Total CMS Domain (domain), required.
  • License Key (license), required; stored as a sensitive connection value.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-totalcms@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 14 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Total CMS connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-totalcms@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com