Resources · Make integration

Tidely Make integrationAutomate Tidely with Make.

Tired of typing invoices into Tidely by hand? The Tidely Make integration gives you 2 action modules: one imports an invoice, the other calls any endpoint of the Tidely API. This page shows how to link your account and build a first scenario that feeds invoices in for you.

Try the Tidely integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tidely Make integration do for you?

The Tidely Make integration lets a Make scenario, the automation you build as a chain of modules, push invoices into Tidely without anyone copying them over. Each module is one brick of that chain; Tidely brings two of them, both actions, so the data comes from another app or from a schedule you set in Make.

Invoices that land in Tidely on their own. Put the trigger of your billing or accounting tool first, then Import an Invoice. Every invoice that reaches Make travels as a bundle, one item passed from module to module, and ends up in Tidely with the values you mapped.

Everything the two modules do not cover. Make an API Call reuses the same connection and reaches any endpoint of the Tidely API. When you need something other than an invoice import, this is the module to open, with the Tidely API documentation next to it.

A clean start on the Free plan. Tidely is a standard app in Make, so you can test it without paying Make. Keep in mind that every module run counts as an operation on your plan. If you are still choosing a platform, read the n8n vs Make comparison or the Make review.

What Make does not do here: there is no Tidely trigger, so Make never notices on its own that something changed inside Tidely. The Make documentation page for Tidely also warns that its content is AI-generated from the vendor docs; check the details with Tidely before relying on them. If a run fails, Make troubleshooting walks through the usual causes.

Connect

How do you connect Tidely to Make?

  1. 01

    Check your Tidely plan and grab the key

    Make only talks to Tidely accounts on a Professional Business or Enterprise subscription. Once you are on one of those, copy the API key from your Tidely account and keep it within reach for the next step.

  2. 02

    Add a Tidely module to a scenario

    Sign in to Make, open a scenario, add Import an Invoice or Make an API Call, then click Create a connection. The Connection name field is optional; a clear name helps once you run several accounts.

  3. 03

    Paste the credentials and save

    Enter the credentials copied from Tidely, or follow the instructions Make shows on screen. The connection, your Tidely account linked to Make once, is then reused by both Tidely modules in every scenario.

First scenario

Your first scenario with Tidely

GoalWhen another app hands Make a new invoice, Make imports it into Tidely.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Tidely has no trigger, this first bubble belongs to the app where your invoices start.

  2. 02

    Set up the starting module

    Search that app by name, pick the module that brings out an invoice, and link your account with Create a connection. Make then lists what it can read from that account.

  3. 03

    Add Import an Invoice

    Click the + on the right of the first module, search Tidely and choose Import an Invoice. Select your Tidely connection, then map each field from the data the first module passes along.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received, so you can open Tidely and confirm the invoice arrived as expected.

  5. 05

    Schedule it and switch it on

    Open the clock on the first module to set the schedule; a new scenario checks every 15 minutes by default. Then switch the scenario on and let it work without you.

Modules

What the Tidely modules do

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

Tidely1

Import an Invoice

ActionIn the docs only

This action takes one invoice coming from earlier in your scenario and records it in Tidely, so nobody has to retype it. One invoice per bundle means one import per run of the module.

When to use it
right after the module of your billing or accounting tool that hands over a fresh invoice.
Watch out
the Make documentation lists no official description for this module, so run a test with Run once and check the result in Tidely before switching the scenario on.
Tidely2

Make an API Call

ActionIn the docs only

With this module you can reach any endpoint of the Tidely API from your scenario, using the Tidely connection you already created. It fills the gap whenever you need more than an invoice import.

When to use it
when Import an Invoice does not do what your process needs and the Tidely API offers the missing request.
Watch out
you build the request yourself, so keep the Tidely API documentation open and test each call with Run once.
Need help

Need help automating Tidely with Make?

A person reads every message.

FAQ

Questions about the Tidely Make integration

01Is the Tidely Make integration free?
Yes, on the Make side. Tidely is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, caps a run at 5 minutes and files at 5 MB, with 512 MB of data transfer. Paid plans go down to a 1 minute interval. Each module run counts as an operation. On the Tidely side, you need a Professional Business or Enterprise subscription to connect at all.
02What do you need to connect Tidely to Make?
You need a Tidely account on the Professional Business or Enterprise subscription and an API key taken from that account. In Make, add a Tidely module to a scenario, click Create a connection, optionally give it a name, then enter the credentials copied from Tidely. The connection is saved once and every Tidely module in your scenarios reuses it, whether it is Import an Invoice or Make an API Call.
03Does the Tidely Make integration react in real time?
No, because Tidely has no trigger in Make. A scenario with Tidely starts from another source: the trigger of another app, placed first in the flow, or the schedule set on the first module, which runs every 15 minutes by default. If the other app offers an instant trigger, meaning it calls Make through a webhook as soon as something happens, the invoice reaches Tidely without waiting for the next scheduled check.
04What if the Tidely module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Tidely API with the connection you already have, so you can go beyond invoice imports without leaving Make. Build the request from the Tidely API documentation and test it with Run once. The Make documentation page for Tidely also says it was generated by AI from the vendor docs, so confirm important details with Tidely. If a call fails, read the bundle Make shows for that module before changing the request.
05Should you use Make or n8n for Tidely?
It depends on the tool your team already works in. Make offers a ready Tidely app with 2 action modules, Import an Invoice and Make an API Call, plus a guided editor where you test with Run once before switching a scenario on. n8n has nodes for many apps, so check whether one covers Tidely and what it exposes. Pick the tool whose Tidely coverage matches your process, not the brand name.
Same platform

Other docs you might need on this stack.

Browse all integrations