Resources · Make integration

Put.io Make integrationAutomate Put.io with Make.

Can a link found in another app land in Put.io without copy and paste? The Put.io Make integration gives you 2 modules: one adds a URL transfer, the other calls the Put.io API directly. This page connects your account and walks you through a first working scenario.

Try the Put.io integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

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

The Put.io Make integration links your Put.io account to Make, a visual tool where you build a scenario: an automation made of modules, each module being one brick such as an action. Here, the main brick sends a URL to Put.io as a new transfer, so a link collected somewhere else ends up in your cloud storage without you opening Put.io.

Links from a form, queued automatically. A form tool or a spreadsheet collects URLs; Make passes each one to Adds a Transfer to Put.io, and every submitted link becomes a transfer in your account. The 123FormBuilder Make integration shows how such a form feeds a scenario.

A shared link turned into a transfer. When a teammate posts a URL in a chat tool, the scenario picks it up and hands it to Put.io, so nobody has to switch tabs to start the transfer.

Anything the listed modules skip. Put.io has only 2 modules in Make. For other parts of its API, Make an API Call reuses your connection and reaches any action the Put.io API offers, which suits builders at ease with technical docs.

What Make does not offer here: no trigger. Nothing inside Put.io can start a scenario on its own, so the flow always begins in another app or on a schedule. The same app often exists as an n8n node too; the n8n vs Make comparison lays out the criteria, and the Make training covers the editor from the ground up.

Connect

How do you connect Put.io to Make?

  1. 01

    Create an app in Put.io

    In your Put.io account, open the API section from the account menu and click Create App. Give it a name, paste the callback URI https://www.integromat.com/oauth/cb/put-io, click Save, then the key icon to see your credentials.

  2. 02

    Copy the two credentials

    Put.io now displays a Client ID and a Client secret. Copy both somewhere safe for a moment. These are what Make uses to reach your account; you need an active Put.io account to get them.

  3. 03

    Create the connection in Make

    Add a Put.io module to your scenario and click Create a connection. The Connection name field is optional. Paste the credentials or follow the on-screen instructions, and the connection (your Put.io account linked to Make) is reused by both modules.

First scenario

Build your first Put.io scenario

GoalWhen a new link shows up in another app, Make adds it to Put.io as a transfer.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app where your links appear, for example a form or a sheet, as the first module.

  2. 02

    Add the Put.io action

    Click the + on the right of that first module, search for Put.io and choose Adds a Transfer to Put.io. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the URL

    Fill the module by mapping the link from the previous module. Each bundle, meaning one item passed along, such as one form entry, carries its own URL into the Put.io module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubbles above each module to read the bundles it received, then check Put.io for the new transfer.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario checks every 15 minutes by default. Switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Modules

What the Put.io modules do

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

Put.io1

Adds a Transfer to Put.io

Action

In Make“Add a url transfer to put.io cloud storage and file transfer service.”

Hand this module a URL and it adds a matching transfer to your Put.io account, so the link ends up in your cloud storage without a manual paste.

When to use it
whenever a link arrives in another tool, a form answer or a new sheet row, and should go straight into Put.io.
Watch out
the module acts on one bundle at a time, so a list of links runs it once per link, and each run is an operation.
Put.io2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This one gets you everything the transfer module does not cover: it sends an authorized request to any action of the Put.io API, reusing the connection you already created.

When to use it
once you have found in the Put.io API documentation an action that Make does not list as a module.
Watch out
you write the request yourself, path and body included, so read the vendor documentation before your first Run once.
Need help

Need help automating Put.io with Make?

A person reads every message.

FAQ

Put.io and Make: frequent questions

01Is the Put.io Make integration free?
Yes, Put.io is a standard app, available from the Make 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, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your Put.io subscription is separate and handled on the Put.io side.
02What do you need to connect Put.io to Make?
An active Put.io account and API credentials. In Put.io, open the API section of the account menu, click Create App, enter a name and the Make callback URI, then save. The key icon next to the app reveals the Client ID and the Client secret. Back in Make, click Create a connection on a Put.io module, optionally name the connection, and paste those credentials or follow the on-screen steps. Make then reuses that connection in both Put.io modules.
03Does the Put.io Make integration have a trigger?
No. Put.io has no trigger module in Make, so nothing in Put.io can start a scenario by itself. The scenario begins with another app, for example a form or a sheet whose trigger watches for new entries, or with the schedule set on the first module, every 15 minutes by default. Put.io then comes in as the action that adds the transfer, one transfer for each bundle the first module passes along to it.
04What if the Put.io Make module you need is missing?
It depends on the Put.io API. Make lists only 2 modules for Put.io, and one of them, Make an API Call, fills the gaps: it calls any action of the Put.io API with the connection you already set up. You describe the request yourself, so keep the Put.io API documentation open. The Make documentation for this app notes that its content is AI-generated, so confirm important details with Put.io directly.
05Should you use Make or n8n for Put.io?
It depends on your criteria. In Make, Put.io offers 2 modules, a transfer action and a generic API call, and you build the scenario visually with a guided connection. The same app often exists as an n8n node as well. Compare the modules each tool lists for Put.io, the way you prefer to build, and where your other apps already live, then pick the tool your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations