Resources · Make integration

Raklet Make integrationAutomate Raklet with Make.

Your Raklet members, tags and payments can move on their own. The Raklet Make integration offers 20 modules: 2 triggers, 15 actions and 3 searches. This page walks a Make beginner through the connection, a first working scenario and every module.

Try the Raklet integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Raklet Make integration do for you?

The Raklet Make integration links your Raklet account to Make so that contacts, tags, notes and payments update without manual copy and paste. You build a scenario, the automation itself, from modules: small bricks that each watch, read or change one thing in Raklet.

Every payment leaves a trace on the member file. Watch New Payment spots each processed payment, and Add a Note on a Contact writes a short line on the contact, so whoever opens the file sees what happened without digging.

New members land in the right segment. Watch New Contact picks up each contact created in Raklet, and Add a Tag on a Contact labels it straight away. Remove a Tag from a Contact does the reverse when someone changes status.

Your tag list stays tidy. Search Tags, Create a Tag, Update a Tag and Delete a Tag let a scenario keep the tag catalog in line with another tool instead of editing it by hand.

The listed modules stop at payments, contacts, notes and tags. For anything else in the Raklet API, Make an API Call reuses the same connection. The documentation gives no numeric limit for this app. Raklet also has an n8n node; the n8n vs Make comparison helps you choose, and the Make training covers the editor from zero. If a run fails, start with Make troubleshooting.

Connect

How do you connect Raklet to Make?

  1. 01

    Open a Raklet module

    You need a Raklet account first, created on raklet.com. In Make, add any Raklet module to a scenario, then click Add next to the Connection field. The connection is your Raklet account linked to Make once, then reused by every Raklet module.

  2. 02

    Name the connection

    In Connection name, type something you will recognize later, such as the name of your association or community. It only matters inside Make, but a clear name saves confusion when several accounts sit side by side.

  3. 03

    Enter your Raklet login

    Fill Email and Password with the credentials you use to sign in to Raklet, then click Save. Make can now read and change your Raklet data from any module of this app.

First scenario

Your first scenario: tag every new Raklet contact

GoalWhen a contact is created in Raklet, Make adds a tag to that contact.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Add Watch New Contact

    Search for Raklet, pick Watch New Contact and choose your connection, or click Add to create it with the three steps above.

  3. 03

    Add the tag action

    Click the + to the right of the trigger, pick Add a Tag on a Contact, map the contact coming from the trigger and choose the tag Make lists from your account.

  4. 04

    Test with Run once

    Create a test contact in Raklet, then click Run once. Open each module to read the bundle it received: one bundle is one item, here one contact.

  5. 05

    Schedule and switch on

    On the first module, set the schedule; a new scenario checks every 15 minutes by default. Switch the scenario on and new contacts get their tag without you.

Triggers

What starts a Raklet scenario?

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

Raklet1Watch New Payment

Watch New Payment

Scheduled trigger

In Make“Triggers when a new payment has been processed.”

Every payment processed in Raklet becomes a starting point: this trigger hands each new one to the rest of your scenario as a bundle, so the follow-up happens without anyone checking the payment list.

How it fires
scheduled. Make checks Raklet on the scenario's schedule, every 15 minutes by default, and on the Free plan never more often than that.
When to use it
when a membership fee or a donation comes in and you want a note, a tag or a message in another tool to follow.
Watch out
each payment picked up becomes a bundle, and every module that handles it counts one operation, the unit Make counts on your plan.
Raklet2Watch New Contact

Watch New Contact

Scheduled trigger

In Make“Triggers when a new contact has been created.”

Newcomers stop slipping through: this trigger passes each contact created in Raklet to the next module, whether it came from a signup form or was typed in by a volunteer.

How it fires
scheduled. Make asks Raklet for new contacts on the scenario's schedule, so a new member shows up at the next check, not the second it is saved.
When to use it
to tag, welcome or copy every new member into another tool as soon as the next check picks it up.
Watch out
it reacts to creations only; an edited contact does not start the scenario again.
Modules

What can Make do in Raklet?

Raklet gives you 18 modules in 4 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Contacts

7 modules
Raklet1

Search Contacts

Search

In Make“Searches for contacts or lists them all.”

Finding the right member before acting on them is what this search gives you: it looks for contacts matching your criteria, or returns the full list, as separate bundles.

When to use it
when another app sends an email address and you need the matching Raklet contact before updating or tagging it.
Watch out
a search can return zero, one or many contacts, and every later module then runs once per result.
Raklet2

Get a Contact

Action

In Make“Retrieves a contact.”

You get the complete record of one contact you already know, so later modules can use its details instead of guessing them.

When to use it
after a trigger or another module gives you a contact identifier, and you need the rest of that member's information for an email or a sheet.
Watch out
it needs a precise contact; if all you have is a name or an address, start with Search Contacts.
Raklet3

Create a Contact

Action

In Make“Creates a new contact.”

People who sign up elsewhere appear in Raklet without retyping: this action adds a new contact from the data of the previous module.

When to use it
when a registration form, an event tool or a spreadsheet collects new members and Raklet should hold them too.
Watch out
to avoid duplicates, put Search Contacts in front and create only when the search finds nobody.
Raklet4

Update a Contact

Action

In Make“Updates a contact.”

Changes made in another tool reach the Raklet file, so the member record stays current without a second round of manual edits.

When to use it
a member changes phone number or address in your form tool or CRM, and the same change should land in Raklet.
Watch out
the module needs the exact contact to change; pair it with Search Contacts when the other app only knows an email address.
Raklet5

Delete a Contact

Action

In Make“Deletes a contact.”

Removing a person from Raklet becomes part of a process instead of a manual cleanup, which helps when someone asks to leave your community.

When to use it
when a removal request arrives through a form and the contact must disappear from Raklet as well.
Watch out
a deletion cannot be undone from Make. Test with Run once on a dummy contact before letting it run on real members.
Raklet6

Add a Tag on a Contact

Action

In Make“Adds a tag on a contact.”

Segmenting your members stops being a chore: this action puts a tag on a contact, which then drives your lists, filters and follow-ups in Raklet.

When to use it
right after Watch New Contact, or when a payment or event signup should place someone in a segment such as volunteers or donors.
Watch out
if you are not sure the tag exists, check with Search Tags and create it with Create a Tag when needed.
Raklet7

Add a Note on a Contact

Action

In Make“Adds a note on a contact.”

The history of a member builds itself: this action writes a note on the contact file, so anyone opening it later sees what happened and when.

When to use it
to log a payment picked up by Watch New Payment, a support ticket from another tool or the outcome of a phone call.
Watch out
each run adds a new note, so a scenario that fires twice on the same event leaves two notes on the file.

Contact Notes

4 modules
Raklet8

List Contact Notes

Search

In Make“Retrieves a contact notes.”

All the notes kept on one contact come back, one bundle per note, ready to be read, copied or checked by the modules that follow.

When to use it
before archiving a member, to export their history to a document, or to check whether a note about a given event already exists.
Watch out
a contact with many notes produces as many bundles, and each module after it counts one operation per note.
Raklet9

Get a Contact Note

Action

In Make“Retrieves a contact note.”

One specific note is fetched in full, so its text can feed an email, a message or a line in a spreadsheet.

When to use it
when List Contact Notes or another module has already pointed to the note that matters and you only need that one.
Watch out
it needs the identifier of the note itself, not only the contact; without it, list the notes first and pick one.
Raklet10

Update a Contact Note

Action

In Make“Updates a contact note.”

A note that already exists gets corrected or completed, which keeps the file readable instead of stacking a new note for every change.

When to use it
a status note, such as a pending renewal, should switch to paid once another module confirms the payment.
Watch out
to keep part of the old text, fetch the note with Get a Contact Note first and carry it into the update.
Raklet11

Delete a Contact Note

Action

In Make“Delete a contact note.”

Outdated or wrong notes leave the contact file, so the history your team reads stays accurate.

When to use it
when a temporary note, for example a reminder about a missing document, no longer applies because the document arrived.
Watch out
once deleted, the note cannot be brought back from Make. Filter carefully with List Contact Notes so only the intended note is removed.

Tags

6 modules
Raklet12

Search Tags

Search

In Make“Searches for tags or lists them all.”

You learn which tags exist in Raklet, filtered by your criteria or all of them, before a scenario relies on one.

When to use it
to check that a tag is there before Add a Tag on a Contact, or to copy your full tag list into a sheet for a quick review.
Watch out
an empty result is not an error, so decide what the following modules should do when no tag matches.
Raklet13

Remove a Tag from a Contact

Action

In Make“Removes a tag from selected contacts.”

Members leave a segment automatically when their situation changes, so your lists reflect who is really active, lapsed or on a committee.

When to use it
a trial membership ends, a volunteer steps down, or a campaign is over and its temporary tag should come off the selected contacts.
Watch out
the module works on the contacts you select; map them carefully so the tag does not come off the wrong people.
Raklet14

Create a Tag

Action

In Make“Creates a new tag.”

New segments appear in Raklet from another source, without anyone opening the settings to type them in.

When to use it
when a new event, course or campaign starts in another tool and Raklet needs a matching tag before members can be sorted into it.
Watch out
run Search Tags before it, or the scenario may create the same tag again on the next run.
Raklet15

Get a Tag

Action

In Make“Retrieves a tag.”

The details of a single tag come back, which is handy when a later module needs more than its name.

When to use it
when a previous step gives you a tag identifier and you want to show or store the tag's information elsewhere.
Watch out
it reads one tag you already know; to find a tag by its name, Search Tags is the better choice.
Raklet16

Update a Tag

Action

In Make“Updates a tag.”

Renaming or adjusting a tag happens from the scenario, so Raklet follows the naming used in your other tools.

When to use it
a program or a group gets a new name in your main system, and the Raklet tag should change with it.
Watch out
the change affects every contact that carries this tag, so check the target with Get a Tag before running it for real.
Raklet17

Delete a Tag

Action

In Make“Deletes a tag.”

Tags you no longer need disappear from Raklet, which keeps the list short and your filters easy to read.

When to use it
once a campaign or a one-off event is over and its tag has no reason to stay in the catalog.
Watch out
deleting a tag cannot be reversed from Make. Try it with Run once on a test tag, and double-check which tag the scenario targets.

Other

1 module
Raklet18

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the Raklet API allows but the listed modules do not cover becomes reachable, using the same connection you already set up.

When to use it
when you need Raklet data beyond payments, contacts, notes and tags, and no ready-made module does the job.
Watch out
you describe the request yourself, so it asks for Raklet's API documentation at hand. Try the ready-made modules first; they are simpler to maintain.
Need help

Need help automating Raklet with Make?

A person reads every message.

FAQ

Raklet and Make: common questions

01Is the Raklet Make integration free?
Yes, Raklet is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes per execution and 512 MB of data transfer. Paid plans, from Core to Enterprise, lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one execution of one module on one bundle, so a busy scenario uses up a plan faster than a quiet one.
02What do you need to connect Raklet to Make?
A Raklet account, created on raklet.com, and a Make account. In any Raklet module, click Add next to the Connection field, give the connection a name, then enter the email and password you use to sign in to Raklet and click Save. The connection acts with that user's rights, so pick an account that can see the contacts and payments you want to automate. Every Raklet module then reuses the same connection.
03Do Raklet triggers fire instantly in Make?
No. Watch New Payment and Watch New Contact are both scheduled triggers: Make asks Raklet for new items on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. A new payment or contact is therefore picked up at the next check. To change that rhythm, open the clock on the first module; to test without waiting, click Run once.
04What if the Raklet module you need is missing?
It depends on the task, but Make an API Call usually solves it. The 20 modules cover payments, contacts, contact notes and tags. For any other endpoint of the Raklet API, Make an API Call sends the request with the same connection, as long as you describe it from Raklet's API documentation. The Raklet documentation in Make lists no numeric limits, so the listed modules are the simpler starting point whenever one fits.
05Should you use Make or n8n for Raklet?
It depends on the tool you already run. Raklet has an n8n node too, so both can handle this app. In Make, you get 20 ready modules, two scheduled triggers and Make an API Call for the rest of the API, all inside a visual editor with a Free plan to start. If your other automations already live in n8n, staying there keeps everything in one place; otherwise, testing a first scenario in Make costs nothing.
Same platform

Other docs you might need on this stack.

Browse all integrations