Each workflow is a concrete recipe: when the agent runs, what it reads, what it changes, what it does not do and where a person approves. Pick the one closest to your work and adapt the briefing to your team.
An Orkeste agent reads the newest Zendesk tickets every hour, works out the topic, the urgency and the queue each one belongs to, and writes that in an internal note on the ticket. Your team still assigns the ticket; the agent saves them the reading.
Every hour, or when you start it.
An Orkeste agent reads new Zendesk tickets, looks for the answer in your help pages and in the documents it was given, and drafts a reply. The reply waits in Validations; once a person approves it, it is posted to the ticket as a public reply.
Every hour, or when you start it.
An outage report, a cancellation or a key account in trouble should not wait in the normal queue. An Orkeste agent reads new Zendesk tickets every hour, picks out the ones that match your urgency rules and posts them to your support channel in Slack with a one-line summary and the ticket number.
Every hour, or when you start it.
When a conversation passes between people, the next one should not have to read the whole thread. An Orkeste agent reads the conversation, writes down the problem, what has been tried and what is still open, and saves the summary where your team looks: a Notion page, a note on the HubSpot contact or a Slack post.
When you start it for a conversation, or every day for open conversations.
Frustration shows up in a conversation long before it shows up in a churn report. An Orkeste agent reads recent Intercom conversations every day, flags the customers who sound frustrated or mention cancelling, and posts them to your customer success channel in Slack with the message behind each flag.
Every day at the hour you set, or when you start it.
Inbound leads arrive faster than anyone can check them. This guide shows how to set up an Orkeste agent, or a swarm of two, that reads inbound emails, checks HubSpot or Salesforce, applies your qualification criteria, records the lead and drafts a reply. A rep approves every email and every CRM change you choose to keep under review.
Every hour, or when you start it.
This is the Salesforce version of automated lead qualification. An Orkeste agent reads inbound emails, searches Salesforce for the contact, the account and any open opportunity, applies your criteria and posts the qualified leads to your sales channel. It logs the exchange on the record so the rep starts with the context.
Every hour, or when you start it.
The context of a deal lives in email threads and call notes, and rarely reaches Salesforce. An Orkeste agent reads the thread or the notes you paste, finds the matching record and logs an activity with the summary, the next step and the people involved. The rep approves before anything is written.
When you start it with call notes, every day for recent email threads, or on each new Gmail or Outlook email.
Writing a personal follow-up for every open deal takes time nobody has. An Orkeste agent reads the opportunity and its recent activity in Salesforce and drafts a follow-up that builds on the last exchange. The rep approves each email; in Gmail it becomes a draft, in Outlook it is sent.
Every week on the day you set, or when you start it for one deal.
A deal can look healthy in the pipeline long after the buyer has gone quiet. Every Monday, an Orkeste agent queries Salesforce for the open opportunities with the oldest activity, reads what happened last and posts a short list to your sales channel with a suggested next step for each.
Every week on the day and hour you set.
An Orkeste agent prepares a one-page brief before your sales meetings: who the account is, what you have sold them, the open opportunities, the last exchanges and the questions worth asking. It works from Salesforce and your Google Calendar, and posts the brief where the rep will read it.
Every day at the hour you set, for the coming meetings.
Reps write notes and Salesforce lags behind. Paste your notes after a meeting and an Orkeste agent finds the opportunity, proposes the new stage or amount and logs the next step as an activity. Each change waits for the rep to approve it.
When you start it with your notes.
HubSpot stays useful as long as someone keeps it current. This guide covers the four jobs an Orkeste agent can take over in HubSpot today: create contacts and deals from inbound emails, add notes from conversations, update deal stages and amounts, and post a weekly pipeline digest to Slack. Each change can wait for a rep's approval.
Every hour for inbound emails, every week for the digest.
An Orkeste agent takes the topic, the audience and the key points you give it, reads related pages in your Notion workspace and creates a structured brief: angle, outline, pages to link and call to action. Your editor reviews the page and edits it instead of starting from blank.
When you start it with a topic.
A good article deserves more than one share. Paste it, or point the agent to the Notion page where it lives, and an Orkeste agent drafts three or four LinkedIn posts, each with its own angle. You approve the ones you like and they publish on your profile or company page.
When you start it with an article.
Regular posting is what makes LinkedIn work, and the first habit to slip. An Orkeste agent runs every week, takes the next idea from your list in Notion, drafts the post in your voice and waits for your approval. Approve it and it publishes.
Every week on the day and hour you set.
Every release deserves a clear internal announcement, and product managers rarely have time to write one. An Orkeste agent reads the release notes in Notion or Confluence, or the issues completed in Linear, and drafts a short announcement for the teams who need it: what changed, who it helps, what to tell customers.
When you start it after a release, or every week.
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.
Every week on the day and hour you set.
New bug reports arrive half-complete and land on whoever is on triage duty. An Orkeste agent reads each new bug in Jira, comments with the likely component, a severity assessment and a suggested owner, asks for missing reproduction steps and posts the critical ones to your engineering channel.
Every hour, or when you start it.
Turning a planning document into well-formed tickets takes a product manager most of an afternoon. An Orkeste agent reads the planning page in Confluence or Notion, splits it into stories with acceptance criteria and creates the issues in Jira once the PM approves them.
When you start it with a planning page.
An Orkeste agent reads your Linear issues on the schedule you set and writes the sprint update: what shipped, what is in progress, what is blocked and what is at risk. It posts the update to Slack once the engineering lead has approved it.
Every day or every week at the hour you set.
Some issues look on track and have not moved in a week. An Orkeste agent searches Linear for issues in progress with no recent update, comments on each one to ask the owner what is blocking, and posts the list to your engineering channel.
Every day at the hour you set.
Decisions are made in meetings and forgotten by the next quarter. Paste the notes, or point the agent to the Notion page where they live, and an Orkeste agent writes a decision record in Confluence: the context, the options considered, the decision, the owner and the date. The decision owner approves the page before it is created.
When you start it after a meeting.
Meeting notes are written fast and read by nobody. An Orkeste agent reads the notes page in Notion, adds a short summary with the decisions, the owners and the deadlines, and posts the action items to the team's Slack channel.
When you start it after a meeting, or every day for new notes pages.
The inbox list on your Trello board fills up faster than anyone sorts it. An Orkeste agent reads the new cards, decides which list each one belongs to and moves it there. It can also turn requests that arrive by email into cards.
Every hour or every day for the inbox list, or on each new Gmail or Outlook email for requests that arrive by mail.
Your project tracker in Airtable is only as current as the last person who updated it. An Orkeste agent reads the issues in Jira or Linear for each project and updates the matching Airtable record: status, a short progress note and the risks to watch.
Every day or every week.
Airtable bases decay quietly: empty required fields, the same client entered twice, a date in the wrong year. An Orkeste agent reads a table on the schedule you set, lists what looks wrong and proposes fixes. An ops lead approves each fix before the record is updated.
Every day or every week.
Your jobs inbox fills up with applications nobody has time to read. An Orkeste agent reads each application email, summarises it against the criteria of the role and posts the summaries to your hiring channel, so the hiring manager decides faster. It never rejects a candidate.
Every hour or every day.
Interview scheduling is five emails for a thirty-minute call. Tell an Orkeste agent who to interview and with whom; it checks the interviewer's Google Calendar for the next seven days, proposes a slot and creates the event with the candidate and the interviewers once the recruiter approves.
When the recruiter starts it for a candidate.
Onboarding emails go out late or not at all when HR is busy. An Orkeste agent runs every morning, reads your list of new hires and their start dates in Airtable or Notion, and prepares the email that is due for each one: welcome, first-day logistics, first-week check-in. In Gmail the emails become drafts HR sends; from Outlook they are sent once approved.
Every day at the hour you set.
Time-off requests arrive in every channel and get lost in most. An Orkeste agent reads the requests sent to your HR inbox, checks who else on the team is away, and posts a summary to the managers' Slack channel. Once a person approves, it records the absence in Airtable and adds it to the calendar.
Every hour, or every day at the hour you set.
Every new person deserves a proper welcome, written on time. An Orkeste agent reads your list of upcoming arrivals in Airtable or Notion and drafts the Slack announcement for each one: role, team, start date and a line about their background. HR approves the post before it goes to the channel.
Every day or every week.
A review cycle is a calendar problem before it is a people problem. Give an Orkeste agent the cycle dates and the list of managers and reports; it creates the events in Google Calendar or Outlook once HR approves, then posts reminders to managers in Slack before each deadline.
When you start the cycle, then every week until it closes.
A failed payment found a week late is often a lost customer. Every morning, an Orkeste agent lists the payments that failed in Stripe, notes the reason, logs each case in Airtable, posts the list to your finance channel and drafts a short email asking the customer to update their payment method.
Every day at the hour you set.
Chasing overdue invoices is easy to postpone. Every week, an Orkeste agent lists the overdue invoices in Stripe or in your Airtable tracker and drafts a reminder for each: polite, specific, with the amount, the due date and the invoice number. Finance approves; from Outlook the email is sent, from Gmail it becomes a draft.
Every week on the day you set.
If invoices are tracked in Airtable and payments arrive in Stripe, someone has to match the two. An Orkeste agent lists recent Stripe payments and invoices, compares them with your Airtable records, proposes to mark the paid ones and flags anything that does not match. Finance approves each update.
Every day or every week.
Receipts forwarded to a shared inbox pile up until month end. An Orkeste agent reads the receipt emails, takes the merchant, the date and the amount from the email text, assigns one of your expense categories and logs each one in Airtable. Finance approves the entries.
Every day.
Churn shows up in Stripe before it shows up in a board deck. Every week, an Orkeste agent lists the subscriptions that were cancelled or are past due, groups them by plan and posts a short summary to finance and customer success with the customers to call.
Every week on the day and hour you set.
The monthly revenue report is mostly the same work every month. An Orkeste agent reads your revenue table in Airtable, sums the figures by segment, compares them with the previous month and writes the narrative report. It saves the draft to Notion or Google Drive, and finance edits it before it goes to leadership.
When you start it at month end.