Resources · Make integration

Vayne.io Make integrationAutomate Vayne.io with Make.

Your Vayne.io orders can start and finish without you opening the dashboard. The Vayne.io Make integration gives you 7 modules, including 1 trigger and 6 actions. This guide connects your account, builds a first scenario and explains when each module earns its place.

Try the Vayne.io integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Vayne.io Make integration do for you?

The Vayne.io Make integration links your Vayne.io account to Make, a visual tool where you chain apps together without writing code. Each automation is called a scenario, and each brick in it is a module. With Vayne.io, those bricks let you place orders, follow them to completion, read your credits and keep the LinkedIn side of your account healthy.

Orders that start from your own lists. Put Create an Order behind a form, a spreadsheet or a CRM module from another app, and every new request becomes a Vayne.io order with no copy and paste. A marketing lead fills in a request, and the order is created behind it.

Results that reach the right place once they are ready. Watch Completed Order notices finished orders, and Get an Order reads one in full so the next module can send it on, to a sheet, a CRM or a chat message for the growth team.

An account you do not babysit. Get Credits, Check the LinkedIn Authentication and Update the LinkedIn Cookie cover the upkeep: know what balance is left before launching a big order, and spot a broken LinkedIn link early.

What Make does not give you: the official documentation publishes no description for these modules, so expect to read the fields in the editor once your connection exists. Anything outside the 7 modules goes through Make an API Call. Plan limits apply too, see Make pricing. If you are weighing Make against another tool, n8n vs Make lays out the criteria, and Make training helps if scenarios are new to you.

Connect

How do you connect Vayne.io to Make?

  1. 01

    Generate your Vayne.io API token

    Log in to Vayne.io, open the Dashboard, then go to API Settings. Click Generate and copy the API token shown on screen. You need an active Vayne.io account for this page to be available.

  2. 02

    Add a Vayne.io module in Make

    In your scenario, add any Vayne.io module and click Create a connection. The Connection name field is optional; a clear name helps when several teammates share the same Make organization.

  3. 03

    Paste the token and save

    Paste the token you copied and confirm. That connection, your Vayne.io account linked to Make, is now reused by every Vayne.io module, so you enter the token once, not once per module.

First scenario

Your first scenario with Vayne.io and Make

GoalWhen an order is completed in Vayne.io, Make fetches that order in full so the next module can use it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the canvas. That circle is where your first module, the trigger, will sit.

  2. 02

    Add Watch Completed Order

    Search for Vayne.io, pick Watch Completed Order and click Create a connection to paste your API token. Already connected? Select the existing connection from the list.

  3. 03

    Fill in the trigger

    Complete the fields the module shows. Once the connection works, Make can read your account and offers the values it finds, so you pick from a list instead of typing blind.

  4. 04

    Chain Get an Order

    Click the + on the right of the trigger, choose Get an Order and map the order passed along by the trigger. Each finished order travels as one bundle, a single item handed from module to module.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows, above each module, the bundles it received. Open them to check the order data looks right before you go further.

  6. 06

    Schedule it and switch it on

    On the first module, open the clock of Scheduling: a new scenario runs every 15 minutes by default, and the Free plan cannot go lower. Save, then flip the scenario on.

Triggers

Which Vayne.io trigger starts your scenario?

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

Vayne.io1Watch Completed Order

Watch Completed Order

triggerIn the docs only

This trigger hands your scenario the Vayne.io orders that have finished, so whatever comes next works on complete results rather than orders still in progress. It is the only way to start a scenario from Vayne.io itself.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, down to 1 minute on paid plans. It is not an instant webhook, so a finished order waits for the next check.
When to use it
whenever a completed order should trigger a follow-up, such as filing results in a sheet or alerting the rep who asked for them.
Watch out
every check counts as an operation, one module run that Make bills against your plan, even when nothing new has finished.
Modules

What can each Vayne.io module do in Make?

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

Vayne.io1

Check the LinkedIn Authentication

ActionIn the docs only

Gives your scenario an answer on the LinkedIn link attached to your Vayne.io account, as the module name indicates, so you learn about a broken link before an order stalls. Make publishes no further description, so read its output in a Run once test.

When to use it
at the start of a scenario that places orders, before Create an Order.
Watch out
pair it with a filter or an alert, otherwise the check runs and nobody reads the result.
Vayne.io2

Create an Order

ActionIn the docs only

Turns a request coming from elsewhere into a new Vayne.io order, so a request collected in a form or a CRM goes to Vayne.io without anyone retyping it. It is the starting point of most scenarios built on this app.

When to use it
when a request arrives from another app and should become an order without a manual step.
Watch out
the documentation does not say what an order uses up, so start with a small input and check your balance with Get Credits.
Vayne.io3

Get Credits

ActionIn the docs only

Reads your Vayne.io credit balance into the scenario, which means you can decide automatically whether a new order should go out or wait. Nothing in your account changes; it only reports.

When to use it
right before Create an Order, with a filter that stops the flow when the balance looks too low, or at the end of a flow to post the remaining balance in a team channel.
Watch out
the documentation gives no threshold, so pick one yourself.
Vayne.io4

Get an Order

ActionIn the docs only

Fetches one specific order so the modules after it can use its details, whether you want to store results, send them or report on them. Unlike the trigger, it does not look for new orders; you tell it which one to read.

When to use it
after Watch Completed Order, or when another app already holds the reference of an order you placed.
Watch out
map the order from an earlier bundle rather than typing it, or the scenario reads the same order every time.
Vayne.io5

Make an API Call

ActionIn the docs only

Opens the rest of the Vayne.io API to your scenario, reusing the connection you already created, so a need the 6 other modules skip is not a dead end. It is the way to cover what the listed modules leave out.

When to use it
when the Vayne.io API documentation describes an endpoint none of the named modules covers.
Watch out
this is the one module where you need the Vayne.io API docs open next to Make.
Need help

Need help automating Vayne.io with Make?

A person reads every message.

FAQ

Vayne.io and Make: common questions

01Is the Vayne.io Make integration free?
Yes, on the Make side. Vayne.io is a standard app, available on every plan including Free. The Free plan still has limits: 2 active scenarios, at least 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) drop the interval to 1 minute and allow unlimited active scenarios. Your Vayne.io subscription is separate: Make needs an active Vayne.io account, and its pricing page tells you what that costs.
02What do you need to connect Vayne.io to Make?
Two things: an active Vayne.io account and an API token. In Vayne.io, open the Dashboard, go to API Settings, click Generate and copy the token. In Make, add a Vayne.io module, click Create a connection, optionally name it, then paste the token. Make stores it as a Bearer token and reuses that single connection for all 7 modules. If you ever regenerate the token in Vayne.io, remember to update the connection in Make as well.
03Does the Vayne.io trigger in Make work in real time?
No. Watch Completed Order is a scheduled trigger: Make checks Vayne.io on the scenario's schedule instead of being called by the app the moment an order finishes. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan; paid plans go down to 1 minute. Each check uses an operation, even when no order has finished, so a tighter schedule costs more of your monthly credits.
04What if a Vayne.io action is missing from Make?
Use Make an API Call. It sends a request to any endpoint of the Vayne.io API through the connection you already set up, so you do not need a second token. You will have to read the Vayne.io API documentation to write the request. Also keep in mind that the Make documentation for this app gives no description of the modules and is flagged as AI-generated, so check important details against Vayne.io's own documentation or ask Vayne.io directly.
05Should you use Make or n8n for Vayne.io?
It depends on the tool your team already knows. The same app often has an n8n node too, so the choice rarely comes down to Vayne.io itself. On Make, you get 7 ready-made modules, one scheduled trigger and Make an API Call for the rest, all in a visual editor. The fair way to decide is to compare the two platforms on your own criteria, such as how your team builds and maintains flows, rather than on a single app.
Same platform

Other docs you might need on this stack.

Browse all integrations