n8n

The Rasket node has 7 resources. Pick a resource, then what to do with it.

The Rasket Trigger starts a workflow on any of these events. Pick one or more.

• A verified sending domain, for sending. Add one under Domains and publish its records; the domains guide walks through it.
• A Full access API key. A Sending access key can send email but cannot manage contacts or create the trigger's webhook.
• For the trigger, an n8n Rasket can reach. Rasket only delivers webhooks to a public https address. n8n Cloud is one. A self-hosted n8n needs a public https URL, set as n8n's WEBHOOK_URL; one on your own computer or on plain http can't receive them.
• Room for webhook endpoints, for the trigger. Each active workflow that starts with a Rasket Trigger uses one of your plan's webhook endpoints, and so does listening for a test event while it listens.

On a self-hosted n8n, as an owner or admin:

1. Open Settings, then Community nodes, and choose Install.
2. Enter n8n-nodes-rasket as the npm package name, accept the note about community nodes and choose Install.
3. Search for Rasket in the nodes panel. Both nodes are there.

A self-hosted n8n that installs from the command line can also run npm install n8n-nodes-rasket in its custom nodes folder and restart.

1. In Rasket, open API keys and create a key with Full access. Copy it; it is shown once.
2. In n8n, add a Rasket node or trigger, open Credential to connect with and choose Create new credential.
3. Paste the key into API Key and save. n8n checks it by reading your team, and says so if the key is wrong.

The credential acts for the team the key belongs to. Deleting the key under API keys stops every workflow that uses it.

• Pick, don't paste. Templates, segments, campaigns, scheduled emails, topics and custom events are lists to choose from. Switch to By ID to map an ID from an earlier node instead.
• From lists hello@ on each of your verified domains. Switch to Address to use any other address on them, such as Name <you@example.com>.
• Template variables become fields. Pick a template in Send Template, or in Schedule with a template, and each variable of its published version appears by name. A variable without a fallback is required.
• Contact properties and event fields work the same way: each property you set up under Contacts → Properties, and each field an event declares, is a field of its own.
• Simplify, on Get and Get Many for emails, campaigns and templates, returns the most useful fields. Turn it off for the full record.

Pick the events, then activate the workflow. Activating creates a webhook endpoint in Rasket for exactly those events, pointed at the workflow. Deactivating deletes it. You will see these under Webhooks; leave them to n8n.

• Each delivery becomes one item: the event's data, plus event, occurred_at and delivery_id. The events guide shows each event's data.
• Every delivery's signature is checked before the workflow starts. One that fails the check starts nothing. If you rotate the signing secret in Rasket, the trigger picks up the new one on its own.
• Changing the events and saving updates the endpoint the next time the workflow is activated.
• Rasket sends no event when a campaign is sent. To act on sent campaigns, use a Schedule Trigger and Campaign → Get Many with the status Sent.

Ready-made workflows with the nodes already chained. Once n8n has verified the Rasket nodes, they are in n8n's template gallery: search for Rasket there and pick one to start from. Each one also works when built by hand from the nodes listed.

• Send a Rasket email for each new Typeform response. Thank everyone who fills in your form, from your own domain. Typeform Trigger → Rasket, Email → Send.
• Update HubSpot contacts when a Rasket email bounces. Mark addresses that bounced for good in your CRM. Rasket Trigger (Email Bounced) → Filter (permanent bounces) → HubSpot, Contact → Create or Update.
• Add new Rasket contacts to Google Sheets. Keep a sheet of everyone who joins your audience. Rasket Trigger (Contact Created) → Google Sheets, Append Row.
• Post the week's sent Rasket campaigns to Slack. A Monday note of every campaign that went out. Schedule Trigger → Rasket, Campaign → Get Many (status Sent) → Filter (last seven days) → Slack.

n8n can retry a node that failed, and you can re-run an execution, and either sends again. To make a repeat harmless, open Options on the send and map something unique from the trigger, such as its ID, into Idempotency Key. Rasket then answers a repeat within 24 hours with the first email instead of sending a second. The idempotency guide has the details.

Removing something already removed, deleting a deleted contact and canceling a canceled email all succeed, so those are safe to repeat. Event → Send has no such key: a repeat sends the event again.