Resources · Make integration

adsfox Make integrationAutomate adsfox with Make.

Can Make keep your adsfox records and conversion events in sync without code? The adsfox Make integration offers 7 modules: 1 scheduled trigger, 5 actions and 1 search. This guide is for marketers who already use adsfox and are new to Make, and it walks you from the connection to a first working scenario.

Try the adsfox integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the adsfox Make integration do for you?

The adsfox Make integration links your adsfox account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, creates or searches something in an app. With adsfox, those bricks let you react when a CRM value moves, write records, open workspaces and push conversion events without touching code.

Conversions that report themselves. Start a scenario with Watch CRM Record Value, then pass what it finds to Send Conversion Event. When a deal reaches the value you care about, adsfox receives the conversion without anyone copying it by hand.

Leads that land already sorted. A form tool or a spreadsheet can feed Create a Record, and Update a Record Lead Status moves the lead forward once your team has qualified it. Search Records comes first when you need to check whether the contact already exists, so you avoid duplicates.

A clean space for each new client. An agency that signs a new account can open a dedicated area with Create a Workspace as soon as the deal is won in its sales tool.

Be aware that Make's own documentation for adsfox is limited: it lists the module names but does not describe their fields or limits. Expect to discover the options inside each module once your connection exists, and read our Make troubleshooting guide if a run fails. Make an API Call covers anything the listed modules leave out.

If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make training helps you build faster.

Connect

How do you connect adsfox to Make?

  1. 01

    Add an adsfox module

    In a new scenario, click the +, type adsfox and pick any of its modules. Make then asks for a connection, which is your adsfox account linked to Make once and reused by every adsfox module. Click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the client or the workspace it belongs to. Then either approve access on the adsfox page that opens, or paste the key adsfox gives you, depending on what the window asks.

  3. 03

    Save and check

    Click Save. When the connection works, the module fields become available and Make can list what it reads from your account. If the fields stay empty, the authorization did not go through and you should create the connection again.

First scenario

Your first scenario with adsfox

GoalWhen a CRM record value changes in adsfox, Make sends a matching conversion event back to adsfox.

  1. 01

    Create the scenario

    Open the Scenarios page, click Create a new scenario, then click the large + in the middle of the editor to place your first module.

  2. 02

    Place the trigger

    Search for adsfox and choose Watch CRM Record Value. Pick your connection, or create it now with Create a connection if this is your first adsfox module.

  3. 03

    Add the conversion

    Click the + on the right of the trigger and add Send Conversion Event. Map the values the trigger returned into its fields, so each bundle (one item passed between modules) becomes one event.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows, above each module, the bundles it received. Open them to confirm the event carries the right record before going further.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks adsfox, every 15 minutes by default. Then turn the scenario on so it keeps running without you.

Triggers

What starts an adsfox scenario

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

adsfox1Watch CRM Record Value

Watch CRM Record Value

triggerIn the docs only

This trigger gives your scenario a starting point inside adsfox: each time Make checks, it picks up CRM record values and hands them to the next module as bundles. It is the only adsfox trigger.

How it fires
scheduled, going by its name. Make checks the app on the scenario's schedule, every 15 minutes by default and never more often than every 15 minutes on the Free plan.
When to use it
you want a sale, a lead stage or a deal amount recorded in adsfox to set off a follow-up, such as a conversion event or a message to your team.
Watch out
the documentation does not describe which values it watches, so run it once and read the bundles before you build on it.
Modules

What the adsfox modules do

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

adsfox1

Create a Record

ActionIn the docs only

Create a Record adds a new entry to adsfox from data that arrives elsewhere, so new entries appear there without manual input. Each bundle it receives becomes one record.

When to use it
a form, a spreadsheet row or a shop order should end up in adsfox as a fresh record.
Watch out
the documentation says nothing about duplicate checks, so place Search Records before it when the same person may come back.
adsfox2

Create a Workspace

ActionIn the docs only

With Create a Workspace, a new adsfox workspace opens for you from inside a scenario, which saves the setup work each time an account starts. Unlike Create a Record, it builds a container rather than an entry.

When to use it
your sales tool marks a client as signed and you want their dedicated space ready right away.
Watch out
test it with Run once on a dummy client first, since every run creates a real workspace.
adsfox3

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any part of the adsfox API that the other modules leave out, reusing the same connection. It is your fallback, not your first choice.

When to use it
you need an adsfox feature that none of the named modules offers, and you have its API reference at hand.
Watch out
you write the request yourself, so read the returned bundle after Run once to confirm adsfox accepted it before you switch the scenario on.
adsfox4

Search Records

SearchIn the docs only

Search Records finds existing adsfox records for you before you act on them, so the next module updates the right entry instead of creating a new one. It can return zero, one or several bundles.

When to use it
a lead writes in again and you want to know whether adsfox already holds that contact.
Watch out
with several matches, every following module runs once per result, and each run counts as an operation (one module execution on your plan).
adsfox5

Send Conversion Event

ActionIn the docs only

Send Conversion Event tells adsfox that a conversion took place, so the result of a sale or a sign-up shows up where you track your marketing. It is the module that closes the loop between your sales data and adsfox.

When to use it
a payment clears in your shop or a deal closes in your CRM and adsfox should know about it.
Watch out
a test with Run once sends a real event, so point it at test data first.
adsfox6

Update a Record Lead Status

ActionIn the docs only

Update a Record Lead Status moves an existing adsfox record to a new stage for you, keeping your pipeline current without clicking through each lead. It changes one record per bundle.

When to use it
a call is booked or a quote is accepted in another tool and the lead should advance in adsfox.
Watch out
it needs to know which record to change, so pair it with Search Records or with the trigger that returned that record.
Need help

Need help automating adsfox with Make?

A person reads every message.

FAQ

Questions about the adsfox Make integration

01Is the adsfox Make integration free?
Yes, on the Make side. adsfox is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. Your adsfox subscription is a separate matter that this page does not cover.
02What do you need to connect adsfox to Make?
An adsfox account and the right to authorize outside tools on it. Make's documentation lists no specific prerequisite and no official connection steps for adsfox, so the generic Make flow applies: add an adsfox module, click Create a connection, name it if you wish, approve access on the adsfox page or paste the key adsfox provides, then click Save. The connection is created once and every adsfox module in your scenarios reuses it.
03Does the adsfox trigger fire instantly in Make?
No. Watch CRM Record Value is a scheduled trigger, going by its name and its listing: Make checks adsfox on the scenario's schedule rather than being called by adsfox. A new scenario checks every 15 minutes by default. On the Free plan that is also the shortest interval, while paid plans can go down to 1 minute. adsfox has no instant trigger in Make, so a change is picked up at the next check, not the moment it happens.
04What if an adsfox module you need is missing in Make?
Use Make an API Call. It is available for adsfox and calls any endpoint of the adsfox API with the connection you already have, so you are not limited to the 7 listed modules. Keep in mind that Make's documentation for adsfox is limited and does not describe module fields, so have the adsfox API reference open when you write the request, and test with Run once before switching the scenario on.
05Should you use Make or n8n for adsfox?
It depends on your criteria, not on a winner. On the Make side, the facts are clear: 7 adsfox modules, one scheduled trigger, the Make an API Call fallback and availability from the Free plan. The same app often has an n8n node as well, so check whether adsfox has one before you choose, then compare how each tool covers the actions you actually need. The comparison linked higher on this page lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations