Resources · Make integration

Tightly Make integrationAutomate Tightly with Make.

Purchase orders, suppliers and restock suggestions can move on their own. The Tightly Make integration gives you 10 modules: 2 triggers, 3 actions and 5 searches. This guide shows how to link your account and build a first working scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Tightly Make integration automate?

The Tightly Make integration links your Tightly account to Make, a visual tool where you chain apps together without code. Each automation you build there is called a scenario. It reads purchase orders, suppliers, contacts and locations from Tightly, and it can create suppliers or update an order when something happens elsewhere.

Purchasing follow-up without copy and paste. Put Watch created purchase orders at the start of a scenario and every new order becomes a bundle, meaning one item passed from a module to the next. From there, send it to your accounting tool, a shared sheet or a chat channel so the team hears about it.

A supplier list that stays in sync. When a vendor is approved in your CRM or a form, Create suppliers adds it to Tightly. List suppliers helps you check what already exists before you add anything.

Restock decisions in front of the right people. List replenishment recommendations returns what Tightly suggests, and a scenario can pass those items to a buyer's inbox or a planning sheet.

Two limits are worth knowing. Both triggers are scheduled, so Make checks Tightly on the scenario's clock and does not hear about orders the moment they appear. And the Make documentation for this app says its content was AI-generated from Tightly's docs, so check important details with Tightly. For the wider picture, read the Make review, see how plans compare in Make pricing, or weigh the two tools in n8n vs Make.

Connect

How do you connect Tightly to Make?

  1. 01

    Get your Tightly credentials

    Log in to Tightly first. For user-level access, register your user with the Tight API and retrieve the OAuth 2.0 access token. For partner-level access, open the section where partner credentials live and note your client ID and client secret.

  2. 02

    Add a Tightly module in Make

    In a scenario, add any Tightly module and click Create a connection. A connection is your Tightly account linked to Make once, then reused by every Tightly module. You can type a label in Connection name, which helps when you run several accounts.

  3. 03

    Paste the credentials and save

    Enter the token or the client ID and secret you copied, or follow the on-screen instructions. Once saved, the module can read your Tightly data, and Make offers lists of what it finds instead of making you type values by hand.

First scenario

Build your first scenario with Tightly

GoalWhen a new supplier is approved in another app, Make creates that supplier in Tightly.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the app where suppliers get approved, such as your CRM or a form tool, and choose the module that picks up a new record.

  2. 02

    Add Create suppliers

    Click the + on the right of that first module, search for Tightly and pick Create suppliers. Click Create a connection if you have not linked your account yet, using the credentials from the step above.

  3. 03

    Map the supplier data

    Fill the Tightly module with data from the previous module: click inside a field and select the matching value from the first app. Make shows what the earlier module returned, so there is nothing to retype.

  4. 04

    Test with Run once

    Add a test record in the source app, then click Run once. It runs the scenario a single time. Open the bubble above each module to read the bundles it received and check the supplier now shows up in Tightly.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set Scheduling. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Then switch the scenario on so it keeps running without you.

Triggers

Tightly triggers in Make

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

Tightly1Watch created purchase orders

Watch created purchase orders

triggerIn the docs only

This trigger starts your scenario with each purchase order newly created in Tightly, so the rest of the flow works on fresh orders only. Every order arrives as its own bundle, ready to be mapped into the next module.

How it fires
scheduled. Make checks Tightly on the scenario's schedule, every 15 minutes by default, and picks up the orders created since the last check.
When to use it
a buyer raises an order and finance or the warehouse needs to hear about it without anyone forwarding an email.
Watch out
each check that finds orders spends operations, which is how Make counts usage on your plan. Orders that were only edited will not appear here.
Tightly2Watch updated purchase orders

Watch updated purchase orders

triggerIn the docs only

Changes matter as much as new orders, and this trigger hands your scenario each purchase order that was modified in Tightly. Use it to keep a status, a delivery date or a sheet in step with what buyers do in the app.

How it fires
scheduled. Make checks Tightly on the scenario's schedule and returns the orders updated since the previous run.
When to use it
an order moves forward in Tightly and a tracking sheet or a supplier thread should reflect it.
Watch out
if the same scenario later runs Update a purchase order on that order, the next check sees it as updated again. Point the action somewhere else to avoid a loop.
Modules

What the Tightly modules do

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

Tightly1

Create suppliers

ActionIn the docs only

Adds a new supplier to Tightly from data that lives elsewhere, so vendor records stop being typed twice. It is an action: one bundle in, one supplier created.

When to use it
a vendor passes approval in your CRM or through an onboarding form and should exist in Tightly straight away.
Watch out
run List suppliers before it when the same vendor might already be there, or you may end up with duplicates.
Tightly2

List contacts

SearchIn the docs only

Returns the contacts stored in your Tightly account so a scenario can reach the right person. As a search, it can send back zero, one or several bundles, and each one travels through the rest of the flow.

When to use it
you want to email or message the people behind a supplier after an order changes.
Watch out
every returned contact runs the next modules once, which adds operations quickly on a large list.
Tightly3

List locations

SearchIn the docs only

Pulls the locations set up in Tightly, which is handy when a scenario must know where stock or an order belongs. The module is a search, so expect one bundle per location it finds, not a single combined answer.

When to use it
a report or a sheet needs to be split by site, or you want to copy your locations into another tool.
Watch out
a search can come back empty. Decide what the rest of the scenario should do when no location is returned.
Tightly4

List purchase orders

SearchIn the docs only

Gives you the purchase orders already in Tightly on demand, rather than waiting for a trigger to spot new ones. That makes it the pick for catching up, rebuilding a sheet or feeding a report.

When to use it
a scenario starts from another event, like a form or a button, and needs the current orders at that moment.
Watch out
each run returns the orders it finds, new or not. For only new or changed orders, use the two Watch triggers instead.
Tightly5

List replenishment recommendations

SearchIn the docs only

Brings Tightly's restock suggestions into Make, so the people who buy see them where they already work. Each recommendation comes back as its own bundle, which you can route, filter or collect.

When to use it
a buyer wants suggestions dropped into a planning sheet or a team channel instead of opening Tightly to look.
Watch out
a recommendation is a proposal, not an order. Keep a person in the loop before anything turns it into a purchase.
Tightly6

List suppliers

SearchIn the docs only

Reads the supplier list from Tightly and hands each supplier to the next module as a bundle. It answers the question “who do we already buy from?” inside a scenario.

When to use it
right before Create suppliers, to check a vendor is not already there, or to mirror suppliers in a CRM.
Watch out
a long list means many bundles and many operations. Narrow the flow early if you only need one match.
Tightly7

Make an API call

ActionIn the docs only

Reaches any endpoint of the Tightly API with the connection you already set up, so you are not stuck when the listed modules fall short. It is the escape hatch of this app in Make.

When to use it
you need something that none of the other nine modules covers and Tightly's API documentation describes it.
Watch out
you write the request yourself, so read Tightly's API docs first. Make troubleshooting helps when a call returns an error.
Tightly8

Update a purchase order

ActionIn the docs only

Changes an existing purchase order in Tightly with data from earlier in the scenario. You avoid opening each order to edit it by hand when the source of truth sits in another tool.

When to use it
a supplier confirms a change by email or in a portal, and the order in Tightly should follow.
Watch out
the module needs to know which order to change, so map it from a trigger or from List purchase orders. Pairing it with Watch updated purchase orders on the same order can loop.
Need help

Need help automating Tightly with Make?

A person reads every message.

FAQ

Tightly and Make: frequent questions

01Is the Tightly Make integration free?
Yes, Tightly is a standard app in Make, so you can use it on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two 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) remove the cap on active scenarios, allow runs every minute and extend execution to 40 minutes. Usage is counted in operations, one per module run on one bundle. Your Tightly subscription is a separate matter handled with Tightly.
02What do you need to connect Tightly to Make?
An active Tightly account and one of two credential types. For user-level access, register your user with the Tight API and retrieve an OAuth 2.0 access token. For partner-level access, you need the client ID and client secret from the area where partner credentials are managed. In Make, add a Tightly module, click Create a connection, give it a name if you like and paste the credentials. The same connection then serves all 10 Tightly modules.
03Do Tightly triggers fire instantly in Make?
No. Both Tightly triggers, Watch created purchase orders and Watch updated purchase orders, are scheduled. Make checks Tightly on the scenario's schedule, every 15 minutes by default, and collects what changed since the previous check. On the Free plan, 15 minutes is the shortest interval. Paid plans can go down to 1 minute. The app has no instant trigger, which would need Tightly to call Make through a webhook. If you need a faster reaction, a shorter schedule on a paid plan is the lever available here.
04What if a Tightly module is missing in Make?
Use Make an API call. It sends a request to any endpoint of the Tightly API with the connection you already created, so you can cover actions beyond the 10 listed modules. You write the request yourself from Tightly's API documentation. Keep in mind that the Make docs for this app are marked as AI-generated from Tightly's own documentation and may contain errors, so check an endpoint with Tightly before you rely on it in a live scenario.
05Should you use Make or n8n for Tightly?
It depends on the modules you need. In Make, Tightly comes as a ready app with 10 modules: two scheduled triggers on purchase orders, three actions including Make an API call, and five searches. It works on the Free plan. This page does not cover whether n8n offers a Tightly node, so check its node list before comparing. Then weigh the two tools on your own criteria: which modules you would actually use, how your team likes to build, and what your other apps already run on.