Resources · Make integration

Shuttle Payment Links Make integrationAutomate Shuttle Payment Links with Make.

Could your payment links look after themselves once a deal is agreed? The Shuttle Payment Links Make integration gives you 6 modules: 1 trigger and 5 actions. This guide is for people new to Make, and it walks you from the connection to a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Shuttle Payment Links Make integration do for you?

The Shuttle Payment Links Make integration links your Shuttle account to Make so payment links can be created, changed, read or cancelled by a scenario, which is the automation you build in Make as a chain of modules. Each module is one brick: a trigger that starts the flow or an action that does something.

Keep your team informed. Watch Payment Link Notification picks up notifications about your payment links, and Get a Payment Link reads the full record so a later module can post it where your finance team works.

Issue links from another tool. When a quote is accepted in your CRM or a form is submitted, Create a Payment Link produces the link without anyone opening Shuttle. Update a Payment Link and Cancel a Payment Link keep it in line when the deal changes.

Cover the gaps. Make an API Call reaches any endpoint of the Shuttle API with the same connection, for anything the five named modules do not handle.

One honest limit: Make says its documentation for this app is limited, because little public information exists about it. Expect to discover the exact fields inside the module once your account is connected. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make review covers the editor in depth. For a hand with larger builds, see our Make agency.

Connect

How do you connect Shuttle Payment Links to Make?

  1. 01

    Add a Shuttle module

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

  2. 02

    Name it and authorize

    Give the connection a clear name if you like, for example the account or client it belongs to. Then authorize Make on the Shuttle page that opens, or paste the key Shuttle gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. From that point Make can read your Shuttle data, and the module fields start offering lists you pick from instead of values you would have to type by hand.

First scenario

Your first scenario with Shuttle Payment Links

GoalWhen Shuttle sends a payment link notification, Make reads the full link and passes it to the tool your team uses.

  1. 01

    Create the scenario

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

  2. 02

    Add the trigger

    Search for Shuttle Payment Links, pick Watch Payment Link Notification and choose your connection, or create one with the steps above.

  3. 03

    Read the full link

    Click the + on the right of the trigger, add Get a Payment Link and map from the trigger whatever tells Make which link to read, so it fetches the right record.

  4. 04

    Send it where it helps

    Add a third module from another app, such as a chat or a spreadsheet, and map the fields you want to share from the bundle, which is the single item passed from one module to the next.

  5. 05

    Test with Run once

    Click Run once to run the scenario a single time, then open the bubble above each module to read the bundles it received and check the mapping.

  6. 06

    Schedule and switch on

    Set the clock on the first module, which checks every 15 minutes by default, then switch the scenario on so it keeps working without you.

Triggers

What starts a Shuttle Payment Links scenario

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

Modules

What the Shuttle Payment Links modules do

Shuttle Payment Links gives you 5 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Shuttle Payment Links4

Make an API Call

ActionIn the docs only

Lets you call any endpoint of the Shuttle API from your scenario, reusing the same connection, so you are not limited to the five named modules.

When to use it
you need something Shuttle offers that no ready module covers.
Watch out
you write the request yourself, and Make's documentation for this app is limited, so keep whatever API documentation Shuttle provides open while you build it.
Need help

Need help automating Shuttle Payment Links with Make?

A person reads every message.

FAQ

Questions about the Shuttle Payment Links Make integration

01Is the Shuttle Payment Links Make integration free?
Yes, you can start on the Make Free plan, because Shuttle Payment Links is a standard app available on every plan. The Free plan limits you to 2 active scenarios, a minimum interval of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow up to 40 minutes of execution. Make counts usage in operations: one each time a module runs on one bundle, the single item passed between modules. Any cost on the Shuttle side is a separate matter.
02What do you need to connect Shuttle Payment Links to Make?
A Shuttle account and a Make account are the starting point. Make publishes no specific prerequisites or connection steps for this app, so you follow the generic path: add a Shuttle module, click Create a connection, optionally name it, authorize Make on the Shuttle page or paste the key Shuttle provides, then click Save. That single connection is then reused by every Shuttle module in your scenarios, so you only go through it once per account.
03Does the Shuttle Payment Links trigger fire instantly?
No. Watch Payment Link Notification is a scheduled trigger, meaning Make checks Shuttle on the schedule you set on the first module rather than being called the moment something happens. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval; paid plans can go down to 1 minute. Note that the type comes from the module name, since Make's directory gives no description for it. Choose the interval based on how fast your team really needs to know.
04What if a Shuttle Payment Links module is missing in Make?
It depends on what you need, but the app includes Make an API Call, which reaches any endpoint of the Shuttle API with the connection you already set up. That covers requests the five ready modules leave out, such as reading data none of them return. Make states its documentation for this app is limited because little public information exists, so look for the right endpoint in whatever API documentation Shuttle provides and test the call with Run once before relying on it.
05Should you use Make or n8n for Shuttle Payment Links?
It depends on how you like to work and which tool your team already uses. Make gives you 6 ready modules for this app, with a visual editor where each step is a bubble and a scheduled trigger to start from. The same app often exists as an n8n node too, so compare the modules each side offers for the tasks you have in mind. Neither answer is right for everyone: list the actions you need, check that each tool covers them, and pick the one your team will maintain.