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 weekly 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. 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 before you save.

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 step-level approval behavior. Publishing always remains approval-gated.

Set unattended permissions

Use the Permissions view to choose how much the brand’s automations may do without you present.
Unrestricted can delete or remove data in connected services. Review the workflow and provider account before enabling it; daoco may not be able to undo those changes.

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.
Automations reconcile interrupted runs so completed steps are not silently abandoned between retries or monitor checks.