All use cases

Email outreach

Follow-ups that reference what was actually said.

An agent finds the threads that went quiet, reads the conversation, and drafts a follow-up grounded in the last real next step. Onboarding sequences read the account before they send.

How it works

Three steps to a standing task

  1. Step 01

    Connect your inbox and sending domain

    Gmail for the conversations you already have; Resend for lifecycle mail from your own verified domain. The agent uses whichever the task calls for.

  2. Step 02

    Give it the account context

    Connect your CRM and your database so each message reflects what the account has actually done, rather than which day of the sequence they landed on.

  3. Step 03

    Review drafts, then let it send

    Start with drafts waiting in your inbox. Once the writing holds up, move the send step into the agent and it goes out on schedule.

The run

What the agent actually does

Every step below is a real tool call: the agent reaches for the API it needs, reads what it finds, and acts.

Tuesdays at 9:00am

Find threads where I sent the last message 5+ days ago and draft a follow-up referencing what we discussed.

  1. gmail·search sent threads with no reply
  2. gmail·read each thread for the last next step
  3. attio·check deal stage and prior touches
  4. gmail·draft 7 follow-ups in thread

7 follow-ups drafted

  • Each references the last concrete next step
  • 3 include the pricing page they asked for
  • 1 skipped: the deal closed last week
  • All waiting in Drafts for your review

Reach

The tools this agent touches

Each one connects once, and the agent gets its complete API.

This task belongs to Sales & RevOps. See the rest of what that team hands off.

FAQ

Questions, answered

Put an agent on email outreach.

Describe the task, attach a trigger, and let it run around the clock.