Resources · Make integration

Trafft Make integrationAutomate Trafft with Make.

Can Make keep your Trafft customer records up to date on its own? The Trafft Make integration gives you 7 modules: one instant trigger, five actions and one search. This guide is for ops people new to Make, and it takes you from connection to a working scenario.

Try the Trafft integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Trafft Make integration do for you?

The Trafft Make integration links your Trafft account to Make so that customers and clients get created, changed or removed without anyone retyping them. You build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as a trigger, an action or a search.

New signups land in Trafft by themselves. When a lead fills in a form in another app, Create a Customer adds that person to Trafft, so your team stops copying names and emails by hand.

Other tools hear about Trafft right away. Watch Events is an instant trigger: Trafft calls Make through a webhook as soon as something happens, and the scenario can pass the news to your CRM or your team chat.

Records stay clean. Update a Customer Details rewrites a customer's details when they change elsewhere, and Delete a Customer removes someone who asked to leave.

Be aware of one gap: Make says its Trafft documentation is limited, because little public information exists about the app. Fields and event types are best checked in the module itself, and Make an API Call covers what the listed modules leave out. If you are still choosing a tool, read our Make review and the n8n vs Make comparison.

Connect

How do you connect Trafft to Make?

  1. 01

    Add a Trafft module

    In your scenario, pick any Trafft module and click Create a connection. A connection is your Trafft account linked to Make once, then reused by every Trafft module you add later.

  2. 02

    Name it and authorize

    Give the connection a name if you like, which helps when you run several Trafft accounts. Then authorize Make on the Trafft page that opens, or paste the key Trafft gives you if Make asks for one.

  3. 03

    Save the connection

    Click Save. Make now reads your Trafft account, and the module fields fill with what it can see. If nothing shows up, the authorization did not go through, so start the step again.

First scenario

Your first scenario with Trafft

GoalWhen a new lead comes in from another app, Make creates that person as a customer in Trafft.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. That first module is the app where your leads arrive, such as your form tool.

  2. 02

    Set up the lead source

    Pick the trigger of that app, connect its account and choose the form or list to watch. Once the connection exists, Make shows you what it can read, so you just pick from the list.

  3. 03

    Add Create a Customer

    Click the + on the right of the first module, search for Trafft and choose Create a Customer. Link your Trafft account with Create a connection if you have not done it yet.

  4. 04

    Map the lead's details

    Fill the customer fields by clicking the data from the first module: each Trafft field takes the matching detail of the lead. Each lead is one bundle, one item passed from module to module.

  5. 05

    Test with Run once

    Click Run once and send a test lead. Make runs the scenario one time and shows the bundles each module received, so you can open Trafft and check that the new customer is there.

  6. 06

    Schedule and switch on

    Set the clock on the first module; a new scenario checks every 15 minutes by default. Then switch the scenario on, and each new lead becomes a Trafft customer without a copy and paste.

Triggers

What starts a Trafft scenario

1 module starts a scenario when something happens in Trafft. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Trafft as soon as it happens.

Trafft1Watch Events

Watch Events

Instant trigger

In Make“Triggers when a webhook is listened.”

Watch Events hands your scenario whatever Trafft reports, the moment Trafft reports it, so the rest of the flow can react while the information is still fresh. It is the only way in the catalog for Trafft itself to start a scenario.

How it fires
instant, which means Trafft calls Make through a webhook as soon as something happens; there is no polling interval to wait for.
When to use it
any time another tool, like a CRM or a team chat, has to learn about a change in Trafft without delay.
Watch out
Make's documentation does not list which events Trafft sends, so run the scenario once and read the bundle before you map anything.
Modules

What each Trafft module does

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

Trafft1

Create a Client

Action

In Make“Creates a client.”

You get a new client record in Trafft, filled from data that arrived in an earlier module, without opening the Trafft screens at all.

When to use it
your Trafft setup works with clients rather than customers, and a signup or a signed deal in another app should produce one.
Watch out
Make lists both a client and a customer module without explaining the difference, so test on a dummy record and see where it lands in Trafft.
Trafft2

Create a Customer

Action

In Make“Creates a customer.”

This one saves you retyping: each person arriving from another app becomes a customer in Trafft, with the details you mapped from the previous module.

When to use it
a lead form, a checkout or a spreadsheet row should turn into a Trafft customer the moment it appears.
Watch out
nothing in the documentation says Trafft blocks duplicates, so a lead sent twice may create two customers; use a filter upstream if that matters.
Trafft3

Delete a Customer

Action

In Make“Deletes a customer.”

Removing someone from Trafft becomes part of the flow, so a person who asked to leave disappears from your records without a manual cleanup.

When to use it
a deletion request or an unsubscribe logged in another tool must also reach Trafft.
Watch out
a wrong target removes a real customer. Point the module at the right one, and test with Run once on a dummy record first.
Trafft4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

With this module you reach the parts of Trafft that the other modules skip, calling any endpoint of the Trafft API through the connection you already set up.

When to use it
you need something the listed modules do not offer, which is likely given how short the Trafft catalog is.
Watch out
Make has little documentation on the Trafft API, so you will need Trafft's own reference to know which endpoint to call and what it expects.
Trafft5

Update a Customer Details

Action

In Make“Overwrites a customer's details.”

Your Trafft customer file follows changes made elsewhere: when contact details are corrected in your CRM, this module writes the new version into Trafft.

When to use it
another tool is where your team edits contact details, and Trafft has to stay in step with it.
Watch out
the module overwrites the customer's details, so map every field you want to keep, or an empty value may replace good data.
Trafft6

List Available Plans

Search

In Make“Retrieves a list of available plans.”

You get the plans available in your Trafft account as a list, ready to be read by the next modules or copied into a report or a spreadsheet.

When to use it
a later step needs to pick a plan, or you want an overview of your plans inside another tool.
Watch out
as a search, it returns zero, one or several bundles, and every module after it runs once per plan, which counts as one operation each time.
Need help

Need help automating Trafft with Make?

A person reads every message.

FAQ

Trafft and Make: common questions

01Is the Trafft Make integration free?
Yes, Trafft is a standard app, so it works on the Free plan of Make. That plan still has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of run time at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of run time. Usage is counted in operations, one per module run on one bundle.
02What does connecting Trafft to Make require?
A Trafft account and a Make account are all the documentation implies, since Make lists no prerequisite for Trafft. You add any Trafft module, click Create a connection, give it a name if you want, then authorize Make on the Trafft page or paste the key Trafft provides, and click Save. The connection is then reused by every Trafft module of your scenarios, so you only do this once per account.
03Does the Trafft trigger in Make work in real time?
Yes. Watch Events is an instant trigger: Trafft calls Make through a webhook as soon as something happens, instead of Make checking on a schedule. Your scenario starts when the event arrives, with no polling interval involved. The other Trafft modules are actions and a search, so if a flow starts from another app with a scheduled trigger, that first module sets the pace, every 15 minutes by default on a new scenario.
04What if a Trafft module is missing in Make?
Use Make an API Call. It lets the scenario call any endpoint of the Trafft API with the connection you already have, so you are not limited to the six listed modules. Keep in mind that Make itself says its Trafft documentation is limited, because little public information exists about the app. You will need the Trafft API reference to know the endpoints, and a Run once test on dummy data before switching anything on.
05Make or n8n for Trafft: which one fits?
It depends on what you already run. Make gives Trafft 7 ready modules, including an instant trigger and a way to call the rest of the API, and you build everything in a visual editor. The same app often exists as an n8n node too, so if your team already works in n8n, check there first. Compare the modules each side offers for the task you have in mind, rather than picking a tool by reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations