Automations overview
Automations let you react to events with a visual flow. Triggers start a run, filters decide whether the run should continue, and actions do the work your workspace supports. Automations are useful when a task is repeatable, rule-based, and easy to describe as "when this happens, do that."
Use automations to reduce routine follow-up, not to hide important decisions. The best flows are specific, observable, and easy for a teammate to understand later. If a workflow needs judgment, approvals, or copy review, keep those human steps visible.
Building a flow
Open Automations and create or edit a flow. Add nodes for triggers and actions, connect them, and save. Test with realistic data where the product offers a test or dry-run path. Start with one simple flow before building a large graph.
A typical flow includes:
- A trigger, such as a schedule or platform event.
- Optional filters that narrow when the flow should proceed.
- One or more actions, such as creating a post, sending a notification, or preparing follow-up work.
- A saved status so the automation is active only when you are ready.
Name each node clearly. Future you should be able to open the canvas and understand the purpose without clicking every setting. If a node depends on a specific account, channel, brand, or locale, include that context in the body or configuration.
Before turning on a flow, check that connected social accounts still have permission, target channels are correct, and any required team approvals are in place.
Personal vs company scope
Some automations can run in a personal workspace. Others apply when a company workspace is active. Pick the context that matches where the events you care about occur. If the automation references company brands, company social accounts, Shopify stores, or approval flows, build it while that company workspace is active.
Workspace context affects permissions too. A member may be allowed to view an automation but not edit it, or allowed to create posts but not manage billing or company settings. If a flow cannot access a resource, confirm both the active workspace and your role.
For agencies, keep client or brand-specific flows separated and clearly named. This prevents a trigger intended for one brand from publishing or notifying in another brand's context.
Templates
Starter templates may be available to clone common patterns. Use them as a shortcut, then customize labels, recipients, filters, and target accounts. Templates should never be treated as finished until you review every node.
Examples of useful automation patterns include:
- Notify a team when an important post is ready for review.
- Prepare social follow-up when a Shopify product changes status.
- Create a recurring reminder for campaign reporting.
- Route certain post types into an approval flow.
- Trigger a link or campaign task when a launch begins.
When a template includes a social publishing step, confirm that the platform rules still match your content. Automated publishing should be predictable and narrow.
Monitoring runs
After a flow is active, review its run history. Successful runs tell you the automation is doing work. Failed runs tell you where permissions, platform limits, or configuration need attention. Do not ignore repeated failures, especially if the automation is tied to publishing or customer-facing content.
If a run fails, open the run detail, identify the node that failed, and check the payload or error message. Common causes include missing account permissions, a deleted target, an invalid media file, or a platform API rejection.
Safe automation habits
- Start with notifications before automatic publishing.
- Add filters so triggers do not fire too broadly.
- Keep node names clear and specific.
- Review active flows before major campaign launches.
- Disable flows you are not using.
- Use approval flows for high-risk content.
Need more help?
Open a ticket from Help → Tickets (sign in required).