Skip to main content
An automation runs a task on a schedule without you in the loop. You describe what should happen, scope it, set a frequency, and Concord executes it at each interval.

Open Automations

Manage your automations.

​
Setting one up

1

Name it

A clear name, so you can identify it in the list later.
2

Add a filter

Scope it to a brand or a media plan. Concord runs in that context each time.
3

Write the instructions

Describe what should happen, as specifically as you would in a conversation: the report you want, the checks to perform, the changes to prepare.
4

Attach files (optional)

Any reference the run should use — a brief, a targeting list, a template.
5

Set the schedule

Daily, weekly, weekdays, or a custom schedule, with the time of day.
6

Choose who it is shared with

Named teammates, or everyone in the workspace. Leave it empty and the automation is yours alone.
Instructions are written in markdown, with an edit and preview toggle — the same editor as Skills.

​
Running one on demand

Run now executes an automation immediately, without waiting for its next scheduled interval. It behaves exactly like a scheduled run: the same instructions, the same context, the same output on the run, the same report to the people it is shared with. Two things it is good for:
  • Checking a new automation does what you meant before it runs unattended at 8am on Monday.
  • Getting the output when you need it early — the report a day ahead of the schedule, without touching the schedule.
You can also enable or disable an automation at any time without deleting it. A disabled automation keeps its instructions, its schedule, and its history; it simply stops firing until you turn it back on.

​
Starting from a template

New automation offers the templates published to your workspace. Pick one and it seeds the form, which you then own and edit. Writing one from scratch stays one click away.

​
Sharing an automation

An automation carries a Shared with audience: named teammates, or everyone in the workspace. What sharing actually does:
  • The run’s conversation is shared before the agent starts, so it is already theirs when the result lands — nobody has to be added after each run.
  • The report email reaches them too. The creator is in the To field and everyone else is blind-copied, so a report never exposes one teammate’s address to another.
  • Everyone in the workspace resolves at run time. A teammate who joins next month is included without anyone editing the automation.
  • Membership is re-checked at each run. Someone who leaves the workspace stops receiving the conversations and the reports.
Named recipients are capped at 200 per automation. The automation itself stays with its creator: recipients receive each run and its report, not edit rights on the schedule or the instructions.

​
Who gets told what

  • Someone you add gets an invitation naming you, the automation, a one-line summary of what it does, and when it next runs.
  • You get a confirmation when you create one, listing who will receive it.
  • An edit only notifies the people it adds. Saving ten times does not mail your teammates ten times, and an edit that leaves the audience alone sends nothing.
  • A paused automation says so rather than quoting a next run that is not scheduled.

​
Sharing from the conversation

You can also set the audience by asking:
Concord matches teammates against your workspace members. If it cannot find someone, it says so rather than reporting a share that did not happen.

​
What happens when it runs

Concord executes the instructions exactly as it would from a conversation, using your Skills for context. The result is put on the run itself — the report, the findings, the proposed changes — so the conversation holds the output and you can pick the work back up from there.
Concord never emails your advertiser or your client on your behalf. An automation’s output goes on the run, and the report reaches only the workspace members it is shared with.
An automation prepares work; it does not approve it. Anything that would write to an advertising platform still becomes a platform action waiting for a human.

​
Finding an automation

The Automations page is a card grid with search and sort. A live automation shows its schedule in green; a stopped one shows it in grey next to a Paused badge.

​
Run history

Each automation keeps its last runs, with a status per run — completed, failed, running, pending, waiting, cancelled. Open a run to see what it produced, or to find out why one did not finish.

​
Good candidates

  • A weekly performance report ready before your Monday review
  • A daily pacing check across active campaigns
  • An end-of-flight summary at the close of each campaign
  • A recurring QA pass on setups built during the week

​
What not to use them for

An automation is a scheduled task, not a monitor. It runs at its interval and reports what it finds. If you need to know about a condition the moment it happens, ask in the conversation instead — an automation running at 8am will not tell you about something that broke at 2pm.