GuidesMake
Make
Connect Rasket to the other apps you use in Make, without writing code. Send an email when a form is filled in, add a contact when someone pays, or start a scenario the moment an email bounces.
Coming soon: the Rasket app is not listed on Make yet. This page describes it as it will ship.
What you can automate
The Rasket app has seven triggers, nineteen actions and six searchs. A trigger starts a scenario when something happens in Rasket. An action does something in Rasket. A search returns the matching items for the modules after it.
| Trigger | Starts a scenario when |
|---|---|
| Watch Email Events | Triggers when an email you sent through Rasket reaches an event you choose, such as delivered, bounced, opened or clicked. |
| Watch Received Emails | Triggers when an email arrives at one of your Rasket receiving addresses. Add Get a Received Email to read its text and HTML. |
| Watch Contacts | Triggers when a contact is created, updated or deleted in your Rasket audience. |
| Watch Suppressions | Triggers when an address is added to or removed from your suppression list, including every unsubscribe (reason `unsubscribe`). |
| Watch Domains | Triggers when one of your sending domains is added, changes status (such as becoming verified) or is deleted. |
| Watch Automation Runs | Triggers when a run of one of your Rasket automations starts, completes or fails. |
| Watch Sent Campaigns | Triggers when one of your campaigns has been sent. |
| Action | What it does |
|---|---|
| Send an Email | Sends an email from an address on one of your verified domains, written here or from one of your templates, now or at a time you choose. |
| Reschedule an Email | Changes when a scheduled email is sent. |
| Cancel a Scheduled Email | Cancels a scheduled email before it is sent. |
| Get an Email | Gets an email you sent through Rasket, with its latest status. |
| Get a Received Email | Gets an email that arrived at one of your receiving addresses, with its text, HTML and attachment details. |
| Create or Update a Contact | Adds a contact to your Rasket audience, or updates the one with the same email address. |
| Get a Contact | Gets a contact in your Rasket audience by email address or ID. |
| Delete a Contact | Deletes a contact from your Rasket audience. A contact that is already gone counts as deleted. |
| Add a Contact to a Segment | Adds a contact to one of your segments. |
| Remove a Contact from a Segment | Removes a contact from one of your segments. A contact that is not in it counts as removed. |
| Update a Contact's Topic Subscriptions | Subscribes a contact to topics, or unsubscribes them. |
| Add an Address to the Suppression List | Stops Rasket sending to an address. |
| Remove an Address from the Suppression List | Lets Rasket send to an address again. An address that is not suppressed counts as removed. |
| Send a Custom Event | Sends a custom event for a contact, which can start your automations. Each run sends the event again. |
| Create a Campaign | Creates a campaign to a segment, written here or from a template, and sends it now if you choose. |
| Send a Campaign | Sends a draft campaign now or at a time you choose. |
| Send a Test of a Campaign | Sends a test of a draft campaign to up to five addresses. |
| Cancel a Campaign | Cancels a scheduled campaign before it is sent. |
| Make an API Call | Performs an arbitrary authorized API call. |
| Search | What it does |
|---|---|
| List Email Events | Lists the delivery events of an email you sent, oldest first. |
| List Contacts | Lists the contacts in your Rasket audience, newest first, or only those in one segment. |
| List Segments | Lists your Rasket segments. |
| Search Suppressions | Searches your suppression list by address and reason. |
| Search Templates | Searches your Rasket templates by name or alias. |
| Search Campaigns | Searches your campaigns by name or subject. |
Wherever a module needs a template, segment, topic, campaign, event, automation or email, you pick it from a list, or map one from an earlier module.
Templates
Ready-made scenarios for the Rasket app, with their fields already mapped. Search for Rasket among Make's templates and pick one to start from.
- Send a Rasket email for new Typeform responses. Thank everyone who fills in your form, from your own domain.
- Send a Rasket receipt email for new Stripe payments. Your own receipt the moment someone pays.
- Send a Rasket template email for new Shopify orders. Order confirmations from a template you designed.
- Add new HubSpot contacts to a Rasket segment. Keep a segment in step with your CRM.
- Post Rasket bounces and spam complaints to Slack. Hear about delivery problems quickly.
- Post new Rasket received emails to Slack. Read support mail where your team talks.
Before you start
- A verified sending domain, for the send modules. The domains guide walks through it.
- Admin on the team you connect. Only an admin can approve the sign-in.
- Room for webhook endpoints, for the triggers. Each Rasket webhook you add in Make uses one of your plan's webhook endpoints.
Connect your Rasket account
- In a Make scenario, add a Rasket module and choose Add beside Connection.
- Choose Save, then sign in to Rasket if you are not already.
- Rasket shows what Make is asking to do, one line per permission. Pick the project the connection is for and choose Approve. Make names the connection after your team.
There is no API key to create or paste.
The connection acts for that team and is listed under Settings → Connected apps. It lasts 90 days, then Make asks you to reauthorize it. Make also asks sooner if no scenario has used the connection for 30 days, if the admin who approved it leaves the team, or if it is revoked under Connected apps.
Triggers
Every Rasket trigger is instant. When you add a trigger, choose Add beside Webhook and pick the events. Make then creates one webhook endpoint in Rasket for exactly those events, and deleting the webhook in Make deletes the endpoint. Turning a scenario off keeps the webhook: Make holds the events until you turn it back on.
What each run carries
Each run has the Event ID, the Event type (such as email.bounced), when it happened, and Data: the email, contact, suppression, domain or automation run it is about, exactly as Rasket's webhooks send it. The events guide lists every field.
Watch Received Emails
Each run carries the sender, the recipients, the subject and each attachment's details. Add Get a Received Email after it, with the Email ID mapped, for the text and HTML. Set up receiving first: see the receiving guide.
Watch Suppressions and Watch Domains
Watch Suppressions also catches every unsubscribe: its reason is unsubscribe. Add a filter on the reason to act on those alone. Watch Domains reports a domain becoming verified as an update with the status verified.
Watch Sent Campaigns
The one trigger that checks on a schedule, as often as your Make plan runs the scenario: Rasket has no webhook for campaigns. It uses no webhook endpoint.
Actions
Send an Email
| Field | What to put in it |
|---|---|
| Template | Optional. Leave it empty to write the email here. Pick a published template to send it instead: its variables appear as fields, and HTML and Text are ignored. |
| Template variables | One field per variable of the template. Leave one empty to use its fallback. Lists and objects take JSON. If you map the template from an earlier module, give the variables under Variables by name instead. |
| To | Required. Up to 50 addresses. |
| From | A list of your verified domains. Pick one, or map an address such as Name <you@example.com> on one of them. Required unless the template sets a sender. |
| Subject | Required unless the template sets one. |
| HTML, Text | Without a template: give one or both. |
| Send at | Optional. Leave it empty to send now, or pick a time up to 30 days ahead. |
| CC, BCC, Reply-To | Optional. One or more addresses each. |
| Tags | Optional name and value pairs, such as invoice = 1042. They come back on the email's events. |
| Idempotency key | Optional. Map something unique from the trigger, such as its Event ID. A second send with the same key within 24 hours returns the first email instead of sending again. |
It returns the new email's ID. Reschedule an Email and Cancel a Scheduled Email take that ID, or pick from your scheduled emails.
Create or Update a Contact
| Field | What to put in it |
|---|---|
| Required. The contact is matched on it: an existing contact is updated, not doubled. | |
| First name, Last name | Optional. |
| Unsubscribe from everything | Optional. Yes unsubscribes the contact from all marketing. Leave it empty to keep their state. Nothing here resubscribes someone who opted out. |
| Properties | One field per contact property you have set up in Rasket. A value must match the property's type. |
| Add to segments | Optional. Segments the contact is already in are kept. |
| Topics | Optional. Pick a topic and Subscribe or Unsubscribe, as many as you like. |
The segment, topic and delete modules each take the contact's email address or ID. Removing a membership, a contact or a suppression that is already gone succeeds, so a retried run does not fail.
Send a Custom Event
Pick an Event, give the contact's email or ID, and add the payload's values by key. The event starts every automation that listens for it. Each run sends it again, so a retried run sends a second event.
Campaigns
Create a Campaign takes a Segment, a From address, a Subject, and a template or your own HTML and text. Turn on Send now to send it at once. A campaign sends only when it passes Rasket's send checks; if one fails, the module stops with the reason.
Make an API Call
Calls any Rasket API route by its path, such as /domains, with the connection's sign-in. It reaches only what the connection was approved for; to reach more, add the permission under Additional scopes when you create the connection. The API reference lists every route.
Sending each email once
Make can retry a run that failed, and a retry sends again. To make a repeat harmless, map something unique from the trigger, such as its Event ID, into Idempotency key. Rasket then answers a repeat within 24 hours with the first email. The idempotency guide has the details.
Troubleshooting
Make asks you to reauthorize Rasket
Rasket ended the connection: it reached 90 days, went 30 days unused, was revoked under Connected apps, or the admin who approved it left the team. Reauthorize and approve again.
“Approved without the permission this module needs”
The connection was approved before this module existed. Reauthorize it and approve again.
“Webhook endpoint limit” when you add a webhook
Each Rasket webhook in Make holds one endpoint, and your plan allows a fixed number. Delete webhooks you no longer use in Make, or endpoints under Webhooks in Rasket, or move to a larger plan.
A trigger went quiet
If a scenario stays off long enough for Make's queue to fill, Make refuses new events, Rasket retries them and then turns the endpoint off and emails you. Turn the endpoint back on under Webhooks, then turn the scenario on.
You stopped using Make
Revoking Make under Connected apps stops its modules, but not its webhooks: the events still go to Make. Delete those endpoints under Webhooks too. Their URLs end in make.com.
Rate limit or sending quota
A team may make ten requests a second; Make retries a run that goes over. See rate limits. A used-up sending quota is different: the module stops with a message saying so until the quota resets or you raise it under Billing.
Any other refusal
The module shows Rasket's own error message, naming the field it is about. The errors page lists every one.