Skip to main content
Automations run repeatable marketing work for a brand. A workflow can research, read or update integrations, create reports and drafts, send summaries, and prepare social posts in a sequence of up to eight steps.

​
Start with a suggestion or build your own

Open Automations from the sidebar. The suggestion cards include workflows for daily content, social listening, Reddit mentions, breakout posts, campaign launches, and integration handoffs. Suggestions that depend on a social account or integration send you to Connections when the required connection is missing. Daily Content Engine writes one post a day in your brand’s voice. It reads your learned brand voice and your best recent posts, picks an angle that avoids what the last few days covered, and leaves a draft for review. It varies the format across the week, and on a day with nothing worth saying it creates no draft and tells you why rather than filling the slot. Queueing the draft is an optional extra step, and like every queue or publish step it waits for your approval. Choose Build workflow when you want to define the workflow yourself. The first-visit walkthrough explains the workspace and keeps a practice builder open while it introduces goals, triggers, steps, and approvals. It does not save or run the practice workflow.

​
Choose when the workflow starts

Event, change, and threshold triggers require a connected integration. Schedule previews show the interpreted timing and timezone before you save. If you edit the start time or recurrence, confirm the preview again so the next run matches the schedule you intended.

​
Add workflow steps

Steps run in order on one thread, so later steps can use the context and results produced earlier in the same run. Available step types include:
  • Research.
  • Check or update an integration.
  • Write a report.
  • Draft posts.
  • Send a summary through an integration.
  • Schedule or publish approved social posts.
You can reorder steps and set an automation to something stricter than the brand’s autonomy setting. A looser setting requires an explicit grant.

​
Set unattended permissions

Use the Permissions view to choose how much the brand may do without you present. The same setting applies in chat and to every automation that has not been set to something stricter. Deleting or removing data in a connected app always asks. See Approval preferences for per-connection exceptions and access controls.

​
Review and manage runs

  • Select Review to see work waiting for approval separately from ordinary history.
  • Open run history to inspect status, timing, step outcomes, and errors.
  • Use Run now to start an active automation outside its schedule.
  • Retry a failed run to continue with its existing run context.
  • Pause an automation to stop future triggers without deleting its configuration.
  • Archive an automation when you no longer need it.
If the brand’s autonomy setting does not allow the action, the automation pauses and waits until someone approves or denies it. Automations reconcile interrupted runs so completed steps are not silently abandoned between retries or monitor checks. Approval decisions stay tied to the specific run, provider operation, and connection scope that produced the review item. Older runs may show legacy workflow memory references in run history.