An Orkeste agent puts together the weekly marketing digest: what shipped, what is scheduled next week, what is late and the deals that came in. It reads your content calendar in Notion or Airtable and your deals in HubSpot, then posts the digest to Slack once you approve it.
The problem
The weekly update is rebuilt by hand every Friday from four tools, and the version leadership reads is already out of date.
How the workflow runs
Runs: Every week on the day and hour you set.
Read the calendar: The agent reads the content calendar in Airtable or Notion.
Read the pipeline: It lists recent deals in HubSpot to show what came in this week.
Add your figures: Paste traffic or campaign figures in the run if you want them in the digest.
Draft: It writes the digest: shipped, next week, late, new deals.
Approve: The digest waits in Validations for the marketing lead.
Post: The approved digest is posted to the leadership channel in Slack.
The digest reaches the leadership channel only after the marketing lead approves it.
Who does what
Digest writer: Assembles the week from your tools.
Marketing lead (human): Approves the digest before leadership reads it.
What this workflow does not do
Does not pull Google Analytics or ad platform figures; paste them if you need them.
Lists recent HubSpot deals, not your full pipeline history.
Not automatically. The Google Analytics connector lists your properties but does not pull metrics. Paste the figures in the run and the agent writes them in.
Can it send the digest by email?
Yes. From Outlook it is sent once approved; from Gmail it becomes a draft.
Can each team get its own digest?
Yes. Create one agent per team with its own sources and channel.