Resources · Make integration

RevSend Make integrationAutomate RevSend with Make.

Can a gift leave RevSend on its own when something happens in another tool? The RevSend Make integration gives you 10 modules: 2 triggers and 8 actions for digital and physical gifts. This page shows how to link your account, build a first scenario and pick the right module.

Try the RevSend integration on Make See the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the RevSend Make integration do for you?

The RevSend Make integration links your RevSend account to Make, so a scenario (the automation you build in Make, a chain of modules) can create gift campaign links, send digital gift card emails or ship physical gifts, and can watch your RevSend orders. No code involved: you pick modules (the bricks of a scenario, one per step) and fill their fields.

A thank-you that goes out without a reminder. A sales rep closes a deal in the CRM, and the scenario runs Send a Digital Gift Card Email for the new client. Nobody has to remember to open RevSend.

A physical gift, with the address collected for you. When you do not know where a contact lives, Request a Physical Gift Address asks for it; once you have one, Send a Physical Gift to an Address handles the shipment side.

Orders your team can follow. Watch New Orders and Watch Order Status Update bring RevSend orders into Make, so a spreadsheet, a chat channel or a CRM record can follow along.

Know the limits before you start. Make's own documentation for RevSend is marked as limited, because little public information exists about the app, and there is no Make an API Call module. The Execute a GraphQL Query module is the one open door beyond the ready-made actions. If you are still choosing a platform, the n8n vs Make comparison lays out both, Make training covers the editor from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect RevSend to Make?

01
Add a RevSend module
In your scenario, click the + and search for RevSend. Pick any of its modules, then click Create a connection. The connection is your RevSend account linked to Make once, and every RevSend module reuses it afterwards.
02
Name the connection
Giving it a name is optional, yet useful as soon as you have more than one RevSend account, say a sales workspace and a customer success one. A clear name saves you from sending a gift from the wrong account later.
03
Authorize Make and save
Depending on what RevSend asks, either approve Make on the RevSend authorization page or paste the key RevSend gives you. Then click Save, and the module is ready for its fields.

First scenario

Your first scenario: a gift card when a deal is won

GoalWhen a deal is marked won in your CRM, Make sends the new client a RevSend digital gift card email.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. That first module is your CRM, the app where deals get closed.
02
Set the starting point
Pick the CRM module that watches won deals and connect your CRM account. Make then lists what it can read from that account, so you choose from menus instead of typing.
03
Add the RevSend action
Click the + on the right of the CRM module, search RevSend and pick Send a Digital Gift Card Email. Map the client's details from the CRM bundle (one item passing from module to module) into the RevSend fields.
04
Test with Run once
Click Run once, then open the bubble above each module to read the bundles it received. Check that the right person would get the gift before anything goes live.
05
Schedule and switch on
Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each module run counts as an operation, the unit Make counts on your plan.

Triggers

What can start a scenario in RevSend?

2 modules start a scenario when something happens in RevSend. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by RevSend as soon as it happens.

RevSend1Watch New Orders

Watch New Orders

triggerIn the docs only

Watch New Orders hands your scenario each RevSend order that appears, so the rest of your stack learns about it without anyone copying it over. Its name and the Make docs listing point to a scheduled trigger, meaning Make polls RevSend rather than waiting for a call.

How it fires

scheduled, Make checks RevSend on the scenario's schedule (the clock badge on the module), every 15 minutes by default.

When to use it

you want every new gift order logged in a sheet or announced in the team chat.

Watch out

the documentation says nothing about which order details come through, so run it once and read the bundle before mapping.

RevSend2Watch Order Status Update

Watch Order Status Update

triggerIn the docs only

Where the previous trigger reacts to orders being created, this one follows orders that already exist and picks up the ones whose status has moved. That is the trigger for keeping a CRM or a client note in step with the gift's progress.

How it fires

scheduled, Make checks RevSend on the scenario's schedule and not the instant a status changes; the Free plan allows no less than 15 minutes between checks.

When to use it

an account manager should hear about the gift's progress without opening RevSend.

Watch out

the list of possible statuses is not documented, so add a filter only after Run once shows you real values.

Modules

What can RevSend do inside a scenario?

RevSend gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

RevSend1

Create a Digital Gift Campaign Link

ActionIn the docs only

This gets you a link to a digital gift campaign that you hand out yourself, through whatever channel the scenario uses next. The recipient follows the link; RevSend is not asked to deliver anything.

When to use it

the link belongs inside a message another app sends, such as a newsletter or an onboarding email.

Watch out

the output format is undocumented, so read it after Run once before mapping.

RevSend2

Create a Physical Gift Campaign Link

ActionIn the docs only

You come away with a link tied to a physical gift campaign, ready to paste wherever your recipients will see it. It suits cases where the person should open the offer on their own terms.

When to use it

event attendees or webinar guests receive the link in a follow-up message built elsewhere in the scenario.

Watch out

choose it over the Send version only when another module does the sending.

RevSend3

Execute a GraphQL Query

ActionIn the docs only

Here you write your own GraphQL query to RevSend and get back whatever it returns. It is the escape hatch when none of the ready-made modules covers the request you need, since this app has no Make an API Call module.

When to use it

you know GraphQL and need data the other modules do not return.

Watch out

Make's docs give no query examples, so you depend on what RevSend documents on its side.

RevSend4

Request a Physical Gift Address

ActionIn the docs only

Missing a mailing address stops a physical gift cold; this module asks the recipient for it through RevSend, so nobody on your team has to chase it by email. It usually sits before any shipping step.

When to use it

a new contact arrives with a name and an email but no street address.

Watch out

the docs do not say how the answer comes back, so plan how the scenario will pick it up.

RevSend5

Send a Digital Gift Campaign Link

ActionIn the docs only

Your recipient gets the digital campaign link sent to them, with RevSend doing the delivery instead of another app. One module replaces the pair of creating a link and emailing it yourself.

When to use it

a renewal is signed and you want the customer thanked without building a separate email step.

Watch out

sending cannot be undone, so test on your own address with Run once first.

RevSend6

Send a Digital Gift Card Email

ActionIn the docs only

The result is an email carrying a digital gift card, landing straight in the recipient's inbox. It is a gift card itself, not a campaign link the person has to open first.

When to use it

a referral is confirmed or a survey is completed and you want to reward that exact person.

Watch out

every bundle that reaches this module sends one email, so filter upstream if a trigger can return several items.

RevSend7

Send a Physical Gift Campaign Link

ActionIn the docs only

With this module, RevSend itself delivers the physical gift campaign link to the person, who then takes it from there. You skip building the message in another app.

When to use it

a prospect books a meeting and you want a tangible gift offered straight away, letting them handle the details.

Watch out

pick Create a Physical Gift Campaign Link instead if the link must sit inside a message you write.

RevSend8

Send a Physical Gift to an Address

ActionIn the docs only

When the address is already known, this module sends the physical gift to it directly, with no link and no step left to the recipient. It is the most direct route from event to parcel.

When to use it

your CRM already stores a verified shipping address for the customer.

Watch out

a wrong or outdated address means a lost gift, so map it from a field you trust.

Need help

Need help automating RevSend with Make?

A person reads every message.

FAQ

RevSend and Make: common questions

01Is the RevSend Make integration free?

Yes, on the Make side. RevSend is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations per month. What RevSend charges for gifts is a separate matter, handled on the RevSend side.

02What do you need to connect RevSend to Make?

A RevSend account and access to its authorization page or key. Make's documentation lists no specific prerequisite for RevSend and gives no official connection steps, so the generic Make flow applies: add a RevSend module, click Create a connection, optionally name it, authorize Make or paste the key RevSend provides, then click Save. The connection is created once and reused by every RevSend module. Run a quick Run once test afterwards to confirm the account answers as expected.

03Does the RevSend trigger in Make react in real time?

No. Both RevSend triggers, Watch New Orders and Watch Order Status Update, appear as scheduled triggers, based on their names and the Make docs listing. Make checks RevSend on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap between two checks; paid plans can go down to 1 minute. A new order or a status change therefore reaches your scenario at the next check, not the moment it happens in RevSend.

04What if a RevSend module you need is missing in Make?

It depends on what you need. This app has no Make an API Call module, so there is no generic request builder. The Execute a GraphQL Query module is the closest alternative if you can write GraphQL and RevSend exposes the data you want that way. Keep in mind that Make's documentation for RevSend is marked as limited. If the gap remains, another app in your scenario may cover that step, or the team at the agency can look at the case with you.

05Should you use Make or n8n for RevSend?

It depends on the platform you already run. On Make, RevSend ships with 10 modules: 2 scheduled triggers and 8 actions covering digital gifts, physical gifts and a GraphQL query. Many apps also have an n8n node, so check whether one exists for RevSend and compare the operations it offers with this list. The practical criteria are the modules each side covers for your use case and the tool where the rest of your automations already live.

Add a RevSend module

Name the connection

Authorize Make and save

Create the scenario

Set the starting point

Add the RevSend action

Test with Run once

Schedule and switch on

Need help automating RevSend with Make?