Workflows

Good work has a next step.

Start with an escalation brief. Prepare a draft, pause for the support lead, then post the reviewed handoff in the right room. Each run keeps its steps and outcomes visible.

Join the waitlistSee it in practice

Mac-only for now. Free during the beta (invite-only).

From context to a reviewed handoff

Put the next step in the process, not in someone’s memory.

Prepare the draft, pause for a decision, and post the reviewed handoff in the right room. Give the next person the context to pick it up.

Source connections → reviewed room output

Prepare the escalation before asking engineering to take over.

  1. The current brief

    Start with a reported access error and approved knowledge from a resolved Jira issue and the Confluence runbook.

  2. An escalation to review

    The workflow brings the relevant guidance into a handoff with the symptoms, attempted fixes, and questions for engineering. The support lead checks it before the final post.

  3. A room handoff

    After approval, the workflow posts the handoff in the selected Them AI room for the next owner.

See support workflows
JiraConfluence
Them AI Prepared for review
Review checkpoint

Confirm the reproduction steps and attempted fixes before the escalation is posted.

Your team decides the next step

Connect Jira and Confluence, then review the imported knowledge. The workflow posts the approved handoff in Them AI; a person updates Jira.

Supplied deal brief + approved memory

Give a proposal a second reading before it leaves the team.

  1. The proposed offer

    Provide the discovery summary, requested deliverables, and the questions left open in the deal notes.

  2. A scope check

    The workflow prepares a proposal outline against approved guidance and pauses for the deal owner to review assumptions.

  3. A reviewed outline

    The final outline lands in the sales room for the rep to use when preparing the customer proposal.

See sales workflows
HubSpotNotion
Them AI Prepared for review
Proposal checkpoint

Confirm the data inputs and implementation owner before agreeing the proposed timeline.

Your team decides the next step

Bring HubSpot notes into the workflow brief and use reviewed Notion guidance. Your rep makes the final update in HubSpot.

Source connections → reviewed room output

Keep the reason for the change beside the release summary.

  1. The change context

    Use approved memory from the merged PR explanation and completed issue, plus the release owner’s current brief.

  2. A technical handoff

    The workflow drafts the change rationale and open release questions, then pauses for engineering review.

  3. An internal summary

    The reviewed summary lands in the engineering room, so support can understand the change and the release owner can see which checks remain.

See engineering workflows
GitHubLinear
Them AI Prepared for review
Release note draft

The retry behavior changed to prevent duplicate work. Confirm the rollout checks with the release owner.

Your team decides the next step

GitHub imports selected repository documents and merged PR bodies. Linear imports completed issue descriptions and documents; workflows do not merge or deploy.

Inside Workflows

A repeatable process, with room for judgment.

Shape the work

Define the handoff before you run it.

Start with a template or your own sequence. Choose the room and specify the symptoms, attempted fixes, sources and open questions the draft should include.

The prepare step in a saved, paused workflow configuration

Define what the first step should prepare.01 / 03

Pause for a person

Put the decision beside the draft.

Add a human approval step before the final post. The room shows when a run needs a decision, and a reviewer can inspect the draft before approving or declining it.

Configuring the human approval step in a paused workflow

Configure a human decision before the final step.02 / 03

Keep the handoff clear

Leave the next owner something useful.

After approval, post the handoff in the selected room. Keep the supporting sources and unresolved checks with it, so the next person knows what to verify and what to do next.

Configuring the final room post after human approval

Set the destination for the reviewed handoff.03 / 03

Explore the full task

Customer support

A subscription billing handoff

Sources, review and next steps Customer success

Customer handoff

Sources, review and next steps Consulting

Workshop to design brief

Sources, review and next steps

A few things worth knowing.

Does choosing a template run it immediately?
No. Choosing a template opens the builder. You review the configuration before creating or running a workflow.
Can I keep a person at the final decision?
Yes. Add a human approval step before the final post. The draft remains visible while the workflow waits for that decision.
How can I see what happened in a run?
Open the run to see each step’s status, output and any error. A run waiting for approval also appears in its room, with a link to the details and decision controls for an authorized reviewer.
Will a workflow send email or update our CRM?
The final workflow post lands in a Them AI room. Your team reviews it and makes any email, CRM or store update in the existing tool.
Does every result become company memory?
No. Workflow output and approved company knowledge are different things. A person decides what to contribute and approve.

Bring one real workflow

Try it on work your team already does.

Choose one recurring question, bring the source material, and name the person who will review the answer. Start there, then decide what is worth repeating.

Mac-only for now. Free during the beta (invite-only). Have a workflow in mind? Plan a pilot with us.