Integration

Connect Intercom to Resend

When something happens in Intercom, your agent does the next thing in Resend. Describe it in plain language and the automation is built, tested on every branch and kept running.

Intercom8 triggersIntercom30 actionsResend28 actions

Browse all apps

Build it

What do you want Intercom and Resend to do together?

Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Or work from Claude Code

Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.

Connect Claude Code

Everything your agent can do with Intercom and Resend

Triggers and actions 8 triggers · 58 actions

Trigger
New company
Fires when a new company is created. Poll GET /companies ordered by created_at.
Trigger
New conversation
Polls for conversations, most recently updated first. Fires for each new conversation.
Trigger
New lead
Instant trigger: fires when a new lead is created in Intercom (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New note on conversation
Instant trigger: fires when a note is added to an Intercom conversation (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New or updated contact
Polls for contacts, most recently updated first. Fires for each new or updated contact.
Trigger
New tag on a conversation
Instant trigger: fires when a tag is added to an Intercom conversation (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New tag on a user
Instant trigger: fires when a tag is added to an Intercom user (webhook). Stub ported from dev.apiant — not yet implemented.
Trigger
New ticket
Fires when a new ticket is created. Poll GET /tickets/search or /tickets ordered by created_at.
Action
Add company
Create (or upsert) a company in Intercom. POST /companies.
Action
Add note to contact
Adds a note to the specified contact as the specified admin.
Action
Add note to conversation
Adds an internal note to the specified conversation as an admin.
Action
Add tag to contact
Attaches a tag to the specified contact.
Action
Add ticket
Create a support ticket. POST /tickets.
Action
Assign conversation
Assigns the conversation to an admin or team.
Action
Close conversation
Closes the specified conversation.
Action
Create contact
Creates a new contact (role user or lead) in Intercom.
Action
Create message
Creates an admin-initiated email or in-app message to a contact.
Action
Delete company
Delete a company by ID. DELETE /companies/{company_id}.
Action
Delete contact
Deletes a contact by ID.
Action
Find admin by email
Fetches an admin's details. Lists all admins; match by email.
Action
Find contact by email
Searches contacts by email and returns matches.
Action
Find tickets
Search tickets by criteria. POST /tickets/search.
Action
Get company
Retrieve a company by ID. GET /companies/{company_id}.
Action
Get contact
Fetches a contact's details by ID.
Action
Get conversation
Fetches a conversation's details by ID.
Action
Get ticket
Retrieve a ticket by ID. GET /tickets/{ticket_id}.
Action
List companies
List all companies. GET /companies.
Action
List segments
List all segments. GET /segments.
Action
List tags
Lists all tags for the workspace.
Action
Open conversation
Opens (marks open) the specified conversation.
Action
Remove tag from contact
Detaches a tag from the specified contact.
Action
Send conversation reply
Sends a reply to the specified conversation as an admin.
Action
Snooze conversation
Snoozes the specified conversation until the given unix timestamp.
Action
Start conversation
Starts a new conversation with the specified contact.
Action
Track event
Submit a data event for a contact. POST /events.
Action
Update company
Update an existing company. PUT /companies/{company_id}.
Action
Update contact
Updates an existing contact specified by ID.
Action
Update ticket
Update an existing ticket. PUT /tickets/{ticket_id}.
Action
Add Contact to Segment
Adds a contact to a Resend segment. You can identify the contact by its ID or email address.
Action
Add Suppression
Adds an email address to your Resend suppression list so no further mail is sent to it.
Action
Cancel Email
Cancels a scheduled Resend email that has not been sent yet.
Action
Create API Key
Creates a new Resend API key. The key itself is returned once, so store it right away.
Action
Create Contact
Creates a contact in Resend. Returns the new contact's ID.
Action
Create Domain
Adds a sending domain to Resend. Returns the DNS records you need to add at your domain host to verify it.
Action
Create Segment
Creates a new segment in Resend for grouping contacts.
Action
Delete API Key
Deletes a Resend API key so it can no longer be used.
Action
Delete Contact
Deletes a contact from Resend. You can identify the contact by its ID or email address.
Action
Delete Domain
Removes a sending domain from Resend.
Action
Delete Segment
Deletes a segment from Resend. The contacts themselves are not deleted.
Action
List API Keys
Returns the API keys on your Resend account, with each key's name and when it was last used. The key values themselves are never returned.
Action
List Contacts
Returns the contacts in your Resend account, optionally limited to one segment.
Action
List Domains
Returns the sending domains on your Resend account and each one's verification status.
Action
List Segments
Returns the contact segments in your Resend account.
Action
List Sent Emails
Returns the emails you have sent through Resend, newest first, with each email's id, sender, recipients, subject, send time and latest delivery event. Supports paging before or after a given email id.
Action
List Suppressions
Returns the email addresses on your Resend suppression list, showing for each one the address, why it was suppressed (bounce, complaint or added manually), the email that triggered it and when it was added.
Action
Remove Contact From Segment
Removes a contact from one of your Resend segments. Identify the contact by its ID or by its email address, and name the segment to take it out of. The contact itself is not deleted.
Action
Remove Suppression
Takes an email address off your Resend suppression list so you can send to it again. Identify it by the suppression ID or by the email address itself.
Action
Retrieve Contact
Returns one contact from your Resend audience, including their name, email address, whether they have unsubscribed, when they were added, and any custom properties stored on them. Look the contact up by its ID or by its email address.
Action
Retrieve Domain
Returns one of your Resend sending domains, including its name, verification status, sending region, tracking settings and the DNS records it needs with each record's current status.
Action
Retrieve Segment
Returns one of your Resend segments by its ID, with the segment's name and when it was created.
Action
Retrieve Sent Email
Returns one email you sent through Resend, with its sender, recipients, subject, HTML and text body, tags, send time and latest delivery event.
Action
Send Batch Emails
Sends up to 100 emails through Resend in a single call. Give it a list of emails, each with a sender, recipients, subject and body, and it returns the id of every email it created.
Action
Send Email
Sends an email through Resend. Set the sender, recipients and subject, provide an HTML or plain text body, and optionally add CC/BCC, reply-to, attachments, tags or a send time.
Action
Update Contact
Updates a contact in your Resend audience. Identify the contact by ID or email address, then change the name, the subscribed/unsubscribed state, or the custom properties. Anything you leave blank stays as it is.
Action
Update Email
Reschedules an email you already queued in Resend, moving it to a new send date and time. Only emails that have not gone out yet can be changed.
Action
Verify Domain
Asks Resend to re-check the DNS records for one of your sending domains and start verifying it. Verification runs in the background, so the domain shows as pending until it finishes.

Each app on its own

The other way round: Resend to Intercom