Resources · Make integration

Authvia Make integrationAutomate Authvia with Make.

Can Make keep your Authvia customers, merchants and conversations in step with the rest of your tools? The Authvia Make integration offers 21 modules, 7 of them triggers. This guide links your account, then walks you through a first working scenario.

Try the Authvia integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Authvia Make integration do for you?

The Authvia Make integration lets Make read and change your Authvia data for you: customers, merchants, merchant products and conversations. You build a scenario, which is the automation you assemble in Make, out of modules, the bricks that each watch, create, fetch or update one kind of record.

Keep customer records aligned. Someone fills in a form in another app, and Create a Customer adds them to Authvia with no retyping. When details change later, Update a Customer edits the same record, and Watch Customer Deleted tells your other tools when a record is gone.

Follow every conversation. Watch Conversation Created starts a scenario for each new thread. Pair it with Get a Customer to pull the matching profile, or use Search Conversations to gather threads before a follow-up. Add a Conversation Message then posts a reply from inside the scenario.

Onboard merchants and their catalog. Create a Merchant sets up the account, Add a Merchant Product fills its catalog, and List Merchant Products shows what is already there, which helps you avoid duplicates.

One honest limit: Make says it cannot yet publish complete documentation for Authvia, because too little public information exists about the app. Expect to discover field names inside the editor once your connection works, and keep the Make troubleshooting guide nearby. For a broader take on the platform, read the Make review. Weighing another tool? The n8n vs Make comparison sets the two side by side.

Connect

How do you connect Authvia to Make?

  1. 01

    Add an Authvia module

    Open a scenario, click the + and search for Authvia. Pick any of its modules, then click Create a connection. A connection is your Authvia account linked to Make once and reused by every Authvia module afterward.

  2. 02

    Name it and authorize

    Give the connection a name if you like, such as the account it belongs to. Then either approve Make on the Authvia page that opens, or paste the key Authvia gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown. Fill one field to confirm it works: once the link is live, Make lists the Authvia records it can read.

First scenario

Build your first scenario with Authvia

GoalWhen a new signup arrives from your web form, Make creates the matching customer in Authvia.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. That first module is where everything starts.

  2. 02

    Set the starting point

    Choose the app that collects your signups, such as your form tool, and pick its trigger. Each new entry becomes a bundle: one item that flows from a module to the next.

  3. 03

    Add Create a Customer

    Click the + on the right, search Authvia and select Create a Customer. Connect your account, then map the name and contact details from the form into the fields Make lists.

  4. 04

    Test with Run once

    Submit a test entry, then click Run once. Open the bubble above each module to read the bundle it received, and confirm the customer shows up in Authvia.

  5. 05

    Schedule and switch on

    On the first module, open the clock and set how often Make checks: every 15 minutes by default. Then flip the scenario on. It now runs without you.

Triggers

Authvia triggers in Make

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

Authvia1Watch Conversation Created

Watch Conversation Created

triggerIn the docs only

Each new Authvia conversation starts your scenario, so a fresh thread can alert a teammate, open a task or log a line in a sheet without anyone watching the inbox.

How it fires
scheduled. Make checks Authvia on the scenario's schedule, every 15 minutes by default, so the scenario reacts on the next check rather than the second the thread opens.
When to use it
you want a record or an alert for every conversation that begins.
Watch out
a busy check can bring back several conversations at once, and each one counts as a separate operation, one execution of one module.
Authvia2Watch Conversation Updated

Watch Conversation Updated

triggerIn the docs only

Changes to an existing conversation, rather than new ones, are what this trigger picks up. It hands each edited thread to the next module so another tool can reflect its latest state.

How it fires
scheduled. Make polls Authvia at the rhythm you set on the scenario's clock.
When to use it
a status or reply in Authvia should update a ticket, a CRM note or a dashboard somewhere else.
Watch out
avoid adding Update a Conversation later in the same scenario. Your own update would count as a change and restart the flow on the next check.
Authvia3Watch Customer Created

Watch Customer Created

triggerIn the docs only

Here the scenario wakes up for every customer added to Authvia, whoever created it. That makes it the natural start for copying new customers into a CRM, a mailing list or an accounting tool.

How it fires
scheduled. On each run of the scenario's schedule, Make asks Authvia for customers it has not seen yet.
When to use it
Authvia is where customers first appear, and other tools need to know.
Watch out
if another scenario already creates customers in Authvia from those same tools, you risk sending records back where they came from. Pick one direction per tool.
Authvia4Watch Customer Deleted

Watch Customer Deleted

triggerIn the docs only

Removing a customer in Authvia should not leave a ghost record elsewhere. This trigger passes each deleted customer to your scenario so you can archive or remove the copy in your other apps.

How it fires
scheduled. Make looks for deletions each time the scenario's schedule comes around.
When to use it
you keep customer lists in several tools and want them cleaned up together.
Watch out
the customer is already gone in Authvia, so a Get a Customer step after this trigger will likely find nothing. Work with the data the bundle carries.
Authvia5Watch Customer Updated

Watch Customer Updated

triggerIn the docs only

When an Authvia customer's details change, this trigger passes the edited record along. Other tools then stay current without anyone copying fields by hand.

How it fires
scheduled. Make checks Authvia for edited customers on the timing you set on the first module.
When to use it
contact details are corrected in Authvia and your CRM or billing tool must follow.
Watch out
never end this scenario with Update a Customer on the same record. Your own update would likely look like a new change, and the scenario could keep feeding itself.
Authvia6Watch Merchant Created

Watch Merchant Created

triggerIn the docs only

A new merchant in Authvia can kick off its whole onboarding: a welcome message, a folder, an internal task. This trigger delivers each new merchant to the rest of the scenario.

How it fires
scheduled. Make queries Authvia for new merchants whenever the scenario's clock says so.
When to use it
merchant accounts are created in Authvia and the team needs a checklist started for each one.
Watch out
if you also create merchants from Make with Create a Merchant, this trigger sees those too. Filter them out if they need different handling.
Authvia7Watch Merchant Updated

Watch Merchant Updated

triggerIn the docs only

Edits on a merchant account travel onward with this trigger, which sends each modified merchant to the next module. Your reports and partner lists stay in line with Authvia.

How it fires
scheduled. Make asks Authvia for changed merchants at the interval set on the scenario.
When to use it
a merchant's details matter in a spreadsheet, a CRM or a shared directory.
Watch out
Update a Merchant inside the same scenario would trigger it again on the next check. Keep the edit and the watch in separate scenarios, or skip the edit.
Modules

Authvia modules in Make

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

Authvia1

Add a Conversation Message

ActionIn the docs only

Your scenario can write into an Authvia conversation, posting a message in an existing thread instead of someone typing it.

When to use it
an event elsewhere, like a paid invoice or a shipped order, deserves a note in the customer's thread.
Watch out
the message lands in a real conversation, so test with Run once on a test thread first.
Authvia2

Add a Merchant Product

ActionIn the docs only

Adds a product to a merchant's catalog in Authvia, so a new item can come straight from a spreadsheet or another tool.

When to use it
products are prepared somewhere else and must appear under the right merchant.
Watch out
run List Merchant Products first if the same product might already exist, or you may create a duplicate.
Authvia3

Create a Customer

ActionIn the docs only

This one turns a form entry, a CRM contact or a sheet row into a new customer record in Authvia.

When to use it
customers are first captured outside Authvia and need to exist there too.
Watch out
the module always creates. If that person may already be in Authvia, check with Get a Customer before deciding between create and update.
Authvia4

Create a Merchant

ActionIn the docs only

Opens a new merchant account in Authvia from data your scenario already holds, such as a signed partner form.

When to use it
merchant onboarding starts in another tool and Authvia should receive the account automatically.
Watch out
a scenario that also listens with Watch Merchant Created will see this new merchant too, so plan for both.
Authvia5

Delete a Customer

ActionIn the docs only

Removes a customer from Authvia when another system says the record should go, keeping your lists consistent.

When to use it
a customer asks to be erased, or a closed account in your CRM must disappear from Authvia.
Watch out
treat the deletion as final. Add a filter before this module and test on a dummy customer first.
Authvia6

Get a Conversation

ActionIn the docs only

Pulls the current state of one Authvia conversation, which is handy when a trigger or a search only gave you its reference.

When to use it
before a reply or a report, you want the latest version of that thread.
Watch out
each call reads a single conversation and uses one operation. Searching is better when you need many.
Authvia7

Get a Customer

ActionIn the docs only

Fetches a single Authvia customer so later modules can use its details, even when your trigger only carried a reference.

When to use it
a conversation or an order arrives and you need the full profile behind it.
Watch out
it needs the identifier of one customer. To find someone without it, start from a search or another trigger instead.
Authvia8

Get a Merchant

ActionIn the docs only

Brings back one merchant's record from Authvia, ready to be mapped into an email, a report or another app.

When to use it
a product, a conversation or an alert refers to a merchant and you want its details beside it.
Watch out
it reads one merchant at a time. For a catalog, pair it with List Merchant Products rather than repeating it.
Authvia9

List Merchant Products

SearchIn the docs only

Returns the products a merchant has in Authvia, one bundle per product, so you can copy the catalog or check it before adding items.

When to use it
you sync a catalog to a sheet or look for a product before creating it.
Watch out
as a search, it can return zero, one or many results, and every module after it runs once per product.
Authvia10

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Authvia API with the connection you already set up, for the cases the other modules do not cover.

When to use it
you need a record type or an action that has no dedicated module in this list.
Watch out
you write the request yourself. With Authvia's documentation incomplete, check the endpoint with the Authvia team before relying on it.
Authvia11

Search Conversations

SearchIn the docs only

Finds Authvia conversations and hands each match to the next module, giving you a batch of threads to report on or follow up.

When to use it
you want the threads linked to one customer, or a set to review, rather than reacting to each new one.
Watch out
a search can come back empty. Add a filter so the scenario handles that case cleanly.
Authvia12

Update a Conversation

ActionIn the docs only

Edits an existing Authvia conversation from your scenario, so its state follows what happens in your other tools.

When to use it
a ticket closes in your help desk, and the matching Authvia thread should show it too.
Watch out
keep it out of any scenario that starts with Watch Conversation Updated. Each edit could set off yet another run.
Authvia13

Update a Customer

ActionIn the docs only

Changes an Authvia customer's details from data coming out of another app, so the record stays correct without manual edits.

When to use it
your CRM holds the master copy and Authvia must follow whenever someone corrects a detail.
Watch out
you need the customer's identifier. A Get a Customer step or the trigger's bundle can supply it.
Authvia14

Update a Merchant

ActionIn the docs only

Rewrites a merchant's information in Authvia so the account matches your source of truth elsewhere.

When to use it
a partner changes details in your onboarding tool and Authvia needs the same values.
Watch out
pairing it with Watch Merchant Updated in one scenario creates a loop. Split them, or filter out changes Make made itself.
Need help

Need help automating Authvia with Make?

A person reads every message.

FAQ

Authvia and Make: common questions

01Is the Authvia Make integration free?
Yes, Authvia is a standard app, so it works on Make's Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes and limits transfer to 512 MB. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Make counts usage in operations: one execution of one module on one bundle. Any Authvia subscription is a separate matter between you and Authvia.
02What do you need to connect Authvia to Make?
An Authvia account is the starting point. Make's documentation for Authvia names no specific prerequisite and admits it is incomplete. In practice you add any Authvia module, click Create a connection, optionally name it, then approve Make on Authvia's page or paste the key Authvia provides, and save. If the window asks for something you cannot find, your Authvia administrator is the person to ask, since the Make documentation does not cover it.
03Do the Authvia triggers in Make fire in real time?
No. The 7 Authvia triggers are treated as scheduled triggers: Make checks Authvia on the scenario's schedule, every 15 minutes by default, and 1 minute at the shortest on paid plans. None is listed as instant, meaning none is called by Authvia through a webhook. The directory was unavailable when this page was written, so this typing comes from the module names. The editor settles it: a clock badge on the module marks a scheduled trigger, a lightning badge an instant one.
04What if the Authvia module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Authvia API with the connection you already created, so a record type or an action without a dedicated module is still within reach. The catch is that you build the request yourself, and Make states that its Authvia documentation is limited because little public information exists. Confirm the endpoint and its parameters with Authvia first, then test the call with Run once on harmless data.
05Should you use Make or n8n for Authvia?
It depends on where the rest of your automations live. On Make, Authvia offers 21 modules: 7 triggers, 12 actions and 2 searches, plus Make an API Call for anything missing. That covers customers, merchants, merchant products and conversations from a visual editor. Whether n8n has an Authvia node is not covered here, so check its catalog before comparing. If your team already runs scenarios in Make, staying there avoids splitting automations across two tools.
Same platform

Other docs you might need on this stack.

Browse all integrations