Email a digest of matching Intercom conversations
A Intercom + Resend agent flow
The conversations a founder actually wants to see, churned-account complaints, anything mentioning a competitor, the word 'cancel', are a handful a day buried in hundreds. Watching the Intercom inbox for them is a tax nobody pays consistently. Let the agent watch instead. It searches conversations with search_conversations against a query you define, collects the matches since the last run, and sends one email with send-email summarizing them: who, the snippet, and a link to each thread. Intercom answers the search when the agent runs it, so the agent reads on a cadence, hourly or twice a day, and a conversation already included in a prior digest is left out of the next.
The flow
search_conversationsSearches conversations using a query to find relevant support threads.
send-emailSends a single transactional email immediately or scheduled, with HTML/text, attachments, CC/BCC, and tags.
Step by step
- Search for what matters
The agent runs search_conversations with your query, scoped to conversations updated since the last digest, and reads back the matching threads with ids and a preview.
- Build the digest
It assembles the new matches into a short email body, one line per conversation with the contact, the snippet, and a link, plus a count at the top. If nothing matched, it sends nothing.
- Send the email
send-email delivers the digest to the people who should see it, from your verified domain, tagged so it threads or filters cleanly in their inbox.
Tell your agent
Twice a day, search Intercom for conversations mentioning 'cancel' or 'refund' updated since the last run, and email me a digest with the contact, a snippet, and a link for each. If there are no matches, send nothing. Don't repeat conversations from the previous digest.
Setup
This flow needs both servers connected to your agent. Follow each install guide:
Worth knowing
- search_conversations returns matching threads with a preview, not the full message history. If the digest needs the actual back-and-forth, the agent calls get_conversation per match for the complete thread, which is an extra read each.
- send-email needs a verified sending domain with SPF and DKIM, or the digest lands in spam. Verify the domain once in Resend before relying on the flow.
- Track which conversation ids you've already sent, keyed on the conversation plus its last update, so a thread that gets a new reply can resurface intentionally rather than being suppressed forever or repeated every run.
Questions
- Can it send only when something matches?
- Yes, and it should. The agent checks the result set first and skips send-email entirely on an empty search, so you don't get a daily email that says nothing happened.
- How fresh is the digest?
- As fresh as the cadence. Intercom doesn't push to the agent, so a conversation that comes in is seen on the next scheduled search. Tighten the interval for near-real-time, loosen it to keep the inbox calm.