Build automations that connect Anthropic to Resend. When something happens in Anthropic, Nodest passes the data along and runs the actions you set up in Resend or the other way around — no coding required.
Pick a ready-made workflow that connects Anthropic with Resend, customise it to fit your needs, and go live in minutes.
When “Product created” fires in Stripe, Nodest will send a message in Anthropic and create a broadcast in Resend.
When “Subscription created” fires in Stripe, Nodest will retrieve a customer in Stripe and send a message in Anthropic and send an email in Resend.
When “Subscription canceled” fires in Stripe, Nodest will retrieve a customer in Stripe and send a message in Anthropic and send an email in Resend.
When “Invoice payment failed” fires in Stripe, Nodest will send a message in Anthropic and send an email in Resend.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a task in Toggl Track.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a task in Todoist.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and send a message in Telegram.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and send a channel message in Slack.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and send an email in Resend.
When “Purchase completed” fires in Easy Digital Downloads, Nodest will send a message in Anthropic and send an email in Resend.
When “Form submitted” fires in Fluent Forms, Nodest will send a message in Anthropic and send an email in Resend.
When “Form submitted” fires in Gravity Forms, Nodest will send a message in Anthropic and send an email in Resend.
When “Issue updated” fires in Linear, Nodest will send a message in Anthropic and send an email in Resend.
When “Member signed up” fires in MemberPress, Nodest will send a message in Anthropic and send an email in Resend.
When “Payment failed” fires in MemberPress, Nodest will send a message in Anthropic and send an email in Resend.
When “Order status changed” fires in WooCommerce, Nodest will send a message in Anthropic and send an email in Resend.
When “User registered” fires in WordPress, Nodest will send a message in Anthropic and send an email in Resend.
When “Task status changed” fires in ClickUp, Nodest will send a message in Anthropic and send an email in Resend.
When “Status changed” fires in Monday.com, Nodest will send a message in Anthropic and send an email in Resend.
When “Bot mentioned” fires in Slack, Nodest will send a message in Anthropic and send an email in Resend.
When “Page content updated” fires in Notion, Nodest will send a message in Anthropic and send an email in Resend.
When “Project update posted” fires in Linear, Nodest will send a message in Anthropic and send an email in Resend.
When “Subscription stopped” fires in MemberPress, Nodest will send a message in Anthropic and send an email in Resend.
When “Project status changed” fires in awork, Nodest will send a message in Anthropic and send an email in Resend.
When “Meeting recap created” fires in Calendly, Nodest will send a message in Anthropic and send an email in Resend.
When “Invitee marked as no-show” fires in Calendly, Nodest will send a message in Anthropic and send an email in Resend.
When “Deal won” fires in Pipedrive, Nodest will send a message in Anthropic and send an email in Resend.
When “Task completed” fires in Todoist, Nodest will send a message in Anthropic and send an email in Resend.
When “Project created” fires in Todoist, Nodest will send a message in Anthropic and create a broadcast in Resend.
When “Message posted” fires in Basecamp, Nodest will send a message in Anthropic and send an email in Resend.
When “Timesheet created” fires in Toggl Track, Nodest will send a message in Anthropic and send an email in Resend.
When “Form submitted” fires in WS Form, Nodest will send a message in Anthropic and send an email in Resend.
When “Booking created” fires in Cal.com, Nodest will send a message in Anthropic and send an email in Resend.
When “Meeting ended” fires in Cal.com, Nodest will send a message in Anthropic and send an email in Resend.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a lead in Pipedrive.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a page in a database in Notion.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create an item in Monday.com.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create an issue in Linear.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a ticket in Intercom.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a task in Google Tasks.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a document in Google Docs.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and quick-add an event in Google Calendar.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a task in ClickUp.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a note in Brevo.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a to-do in Basecamp.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a task in awork.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a task in Asana.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and create a record in Airtable.
When “Email received” fires in Resend, Nodest will send a message in Anthropic and add a note to a contact in ActiveCampaign.
Combine the triggers and actions of Anthropic and Resend to build your automation. Triggers start the automation, and actions are the steps that follow.
ActionList Claude models available to your account.
ActionSend a prompt to Claude and get its reply.
TriggerFires when a contact is added to your Resend audience
TriggerFires when a contact is removed from your Resend audience
TriggerFires when a contact's details or subscription status change
TriggerFires when a recipient's mail server permanently rejects an email
TriggerFires when a recipient clicks a link in an email
TriggerFires when Resend delivers an email to the recipient's mail server
TriggerFires when an email fails to send
TriggerFires when a recipient marks a delivered email as spam
TriggerFires when a recipient opens an email
TriggerFires when Resend receives an inbound email
TriggerFires when an address is added to your suppression list
ActionAdd a Resend contact to a segment.
ActionBlock an address from Resend sending.
ActionStop a queued or scheduled Resend broadcast.
ActionCancel a scheduled Resend email.
ActionCreate a broadcast in Resend.
ActionAdd a contact to your Resend audience.
ActionCreate a custom contact property in Resend.
ActionCreate a segment in Resend.
ActionCreate a subscription topic in Resend.
ActionRemove a broadcast from Resend.
ActionRemove a contact from Resend.
ActionRemove a custom contact property from Resend.
ActionRemove a segment from Resend.
ActionRemove a subscription topic from Resend.
ActionList attachments on an inbound Resend email.
ActionList broadcasts in your Resend account.
ActionList custom contact properties in Resend.
ActionList contacts in your Resend account.
ActionList the contacts in a Resend segment.
ActionList sending domains in Resend.
ActionList published email templates in Resend.
ActionList inbound emails received by your team.
ActionList segments in your Resend account.
ActionList the segments a Resend contact belongs to.
ActionList emails sent from your Resend account.
ActionList suppressed addresses in Resend.
ActionList email templates in Resend.
ActionList a contact's Resend topic subscriptions.
ActionList subscription topics in Resend.
ActionRemove a Resend contact from a segment.
ActionUnblock an address in Resend.
ActionGet one Resend broadcast by id.
ActionGet one Resend contact by id or email.
ActionGet one Resend contact property by id.
ActionGet one Resend sending domain by id.
ActionGet an inbound email's body and headers.
ActionGet one Resend segment by id.
ActionGet one sent Resend email by id.
ActionGet one suppressed address in Resend.
ActionGet one Resend template and its variables.
ActionGet one Resend topic by id.
ActionGet one attachment and its download link.
ActionSend a Resend broadcast to its segment.
ActionSend an email through Resend.
ActionSend a Resend email from a template.
ActionTrigger a Resend automation with an event.
ActionChange a draft broadcast in Resend.
ActionChange a contact's details in Resend.
ActionChange a contact property's fallback value.
ActionReschedule a scheduled Resend email.
ActionRename a segment in Resend.
ActionChange a subscription topic in Resend.
ActionSet a contact's Resend topic subscription.
Create automations that move data between Anthropic and Resend. Nodest handles the work in between, so you can focus on what matters.
Link your Anthropic and Resend accounts to Nodest in a few clicks, so both tools are ready to use in automations.
Choose the event that starts your automation, such as a new order, form submission, or updated record in Anthropic or Resend.
Add one or more actions, and combine them with filters, branches, and delays to create a workflow that fits your needs.
Learn how to take control of your time with automation tips and productivity insights - weekly to your inbox.
