Create an Automation

Automating a workflow that triggers based on content updates and sends data to an external backend service may fail if the design does not account for platform limitations. Improperly configured triggers and actions can result in execution errors or unintended loops.

Root cause

The issue stems from a design validation requirement where the automation logic must be verified for feasibility within Automate, rather than a specific product defect.

Resolution

1. Confirm the intended use case is supported by existing Automate triggers and connectors.
2. Align the automation workflow with best practice patterns for external API integrations.

After configuring the workflow pattern, run a test execution by updating a sample entry. If the payload is received correctly by the backend and no loops occur, the issue is resolved. Escalate with workflow configuration screenshots and execution logs if the issue persists.

Teams may require (a) a manual execution mechanism for automations via API, or (b) the ability to receive inbound webhook calls into Automate.

Root Cause

Automate Management API manages resources (projects/automations) but does not provide a “run automation now” execution endpoint.

Resolution

1. If the requirement is “manual trigger”, implement an HTTP trigger that starts the automation on inbound GET/POST.
2. For event-driven execution from Contentstack:
   • Use Contentstack Webhooks → call an external endpoint (AWS Lambda/Azure Function) → call the Automate HTTP trigger.
3. For governance:
   • Restrict inbound trigger with secret header or token validation at the calling service.

Automation runs reliably when invoked via the configured HTTP trigger endpoint and produces expected downstream actions.

Customers often need content to auto-publish at a defined “end date/time” stored in an entry field, and to automatically update/cancel scheduled jobs if that field changes.

Root Cause

This requires two controlled automation paths: one for new entries and another for updates, including schedule cancellation logic using publish details/job IDs.

Resolution

A) For New Entries

1. Trigger: Entry Create (relevant content type).
2. Step: Read end-date field from payload.
3. Step: Schedule publish action for the same entry at the end-date timestamp.

B) For Updated Entries

1. Trigger: Entry Update (same content type).
2. Fetch previous entry version (CMA) including publish_details.
3. Compare previous end-date vs current end-date (code step).
4. If changed:
   • Identify scheduled job in publish_details matching old scheduled_at.
   • Cancel scheduled job using job_id via CMA cancel schedule endpoint.
   • Schedule publish with new date.

Verify

• New entries are scheduled correctly at the field timestamp.
• Updated entries replace the prior scheduled job with the updated timestamp.
• No duplicate schedules remain active.

Customers want automation to obtain the publishing user’s email when an entry is published and use it for notifications or audits.

Root Cause

The requested attribute may not be available directly in the expected form in the automation payload or may require an alternate extraction approach.

Resolution

1. Confirm what the trigger payload contains (user UID vs email).
2. If only UID is present, resolve user details via a management API call in a code/HTTP step (subject to permissions).
3. Use Email action connector to send notifications using resolved email.

Automation reliably retrieves publisher identity (email or resolved identifier) and uses it in notifications.

Automation actions (e.g., publish) may show attribution to a named user even when using a management token, which can create audit concerns.

Root Cause

Attribution is tied to the account selected during automation configuration, not to the token identity.

Resolution

1. Identify which user account is selected in automation configuration.
2. If audit alignment is required, use an approved service account for automation ownership.
3. Log enhancement request if token-based attribution is required.

Action attribution aligns with the configured automation owner account.