Resources · Make integration

onsft Make integrationAutomate onsft with Make.

Want onsft records to stay in step with the rest of your tools? The onsft Make integration gives you 6 modules: 5 actions and 1 search. This page shows what they do, how to link your account and how to build a first scenario you can test right away.

Try the onsft integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the onsft Make integration do?

The onsft Make integration lets a Make scenario, the automation you build as a chain of modules, work with onsft records without code. Each module is one brick of that chain: here, five actions that act on a single record and one search that finds records, all using the same connection to your onsft account. What a record holds depends on your own onsft account: Make shows its fields once you are connected.

New records without retyping. When a form, a sheet or a CRM in another app produces new data, Create a Record writes it into onsft, and the data you map decides what lands in each field Make shows you.

Records kept current. Search Records finds the entries that match a condition, then Update a Record changes them. Each item that flows between modules is called a bundle, and a search can return zero, one or several of them.

A clean base. Get a Record reads a single entry before you decide what to do with it, and Delete a Record removes the ones you no longer need. When something is missing from the list, Make an API Call reaches any endpoint of the onsft API with your existing connection.

One limit to know up front: the Make help center says it cannot yet offer complete documentation for onsft, because too little public information exists about the app. Test each module with real data before you rely on it. If a run fails, the Make troubleshooting guide covers the usual causes. To learn the editor properly, see Make training, and if you are still choosing a tool, read n8n vs Make.

Connect

How do you connect onsft to Make?

  1. 01

    Add an onsft module

    In your scenario, click the +, type onsft in the search box and pick any of its modules. The first time, Make asks for a connection, which is your onsft account linked to Make once and reused by every onsft module. Click Create a connection.

  2. 02

    Name the connection

    Giving the connection a name is optional, but it helps when you run several onsft accounts or when a teammate opens the scenario later. Something like the account owner or the workspace is enough to tell them apart.

  3. 03

    Authorize and save

    Depending on how onsft signs you in, Make either opens an onsft page where you approve access, or asks you to paste the key onsft gives you. Once that is done, click Save and the module is ready to configure.

First scenario

Build your first scenario with onsft

GoalWhen a change happens in another app, Make finds the matching onsft records and updates them.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app whose event should start the flow, for instance the tool where your team logs a status change.

  2. 02

    Add Search Records

    Click the + on the right of the first module, search onsft and choose Search Records. Create the connection if Make asks, then set the condition using data mapped from the first module.

  3. 03

    Add Update a Record

    Add Update a Record after the search. Map the record returned by Search Records, then fill only the fields you want to change. Make lists what it can read once the connection exists.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time and shows the bundles each module received, so you can check that the right record was found and changed.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. From now on it runs without you.

Modules

What each onsft module does

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

onsft1

Create a Record

ActionIn the docs only

Adds a brand new entry to onsft from data another module passes along, so nobody has to copy it by hand.

When to use it
a lead fills a form or a row appears in a sheet and that information should exist in onsft as well.
Watch out
if the same scenario runs twice on the same input, you get two records, so put Search Records before it when duplicates would hurt.
onsft2

Delete a Record

ActionIn the docs only

Removes one onsft record for good, which keeps the base free of entries that no longer mean anything.

When to use it
a deal is cancelled or a contact asks to be erased, and the matching onsft entry has to disappear too.
Watch out
a deletion cannot be undone from Make. Run the scenario once on a test record and check the bundle before you switch it on.
onsft3

Get a Record

ActionIn the docs only

Reads a single onsft record and hands all its data to the next module, which lets later steps decide based on what is really stored.

When to use it
you already know which record matters, for example one returned by an earlier step, and you need its full content before acting.
Watch out
it reads one record, not a list; when you do not know which entry you want, start with Search Records instead.
onsft4

Make an API Call

ActionIn the docs only

Opens any endpoint of the onsft API from your scenario, reusing the connection you already created, so you are not stuck when a listed module falls short.

When to use it
you need an onsft feature that none of the other five modules offers.
Watch out
this one needs the onsft API reference to fill in, and Make says its own onsft documentation is incomplete, so test each call with Run once.
onsft5

Search Records

SearchIn the docs only

Finds the onsft records that match what you look for and sends each one on as its own bundle, ready for the next module.

When to use it
before an update or a deletion, to reach the right entries from a value another app hands you.
Watch out
the result may be empty or hold several records; every module after it then runs once per record, and each run counts as an operation on your plan.
onsft6

Update a Record

ActionIn the docs only

Changes an existing onsft record with fresh values, so the data in onsft follows what happens in your other tools.

When to use it
a status moves forward in your CRM, a payment clears, a detail is corrected elsewhere and onsft should reflect it.
Watch out
fill only the fields you mean to change and point the module at the record returned by Search Records or Get a Record, not a guessed one.
Need help

Need help automating onsft with Make?

A person reads every message.

FAQ

onsft and Make: frequent questions

01Is the onsft Make integration free?
Yes, onsft is a standard app in Make, so you can use it on the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations: each module that processes one bundle uses one. Whatever onsft itself charges is separate and not covered here.
02What do you need to connect onsft to Make?
You need an onsft account and a Make account. Make's documentation lists no specific prerequisite for onsft. You add any onsft module, click Create a connection, optionally name it, then either approve access on an onsft page or paste the key onsft provides, depending on how the app authenticates, and click Save. The same connection then serves all six modules. Because Make notes that its onsft documentation is incomplete, keep your onsft account settings open in case the connection window asks for something unexpected.
03Does the onsft Make integration react in real time?
No, not by itself, because onsft has no trigger module in Make. A scenario still needs something to start it, and you have two options. The first is a trigger from another app, such as a new form entry or a new sheet row, followed by onsft modules. The second is a schedule on the first module: new scenarios run every 15 minutes by default, and you can shorten that down to 1 minute on a paid plan. Either way, onsft modules act when the scenario runs.
04What if an onsft module is missing in Make?
Use Make an API Call. It is included in the onsft app and can reach any endpoint of the onsft API with the connection you already have, so an action the five other modules do not cover is still within reach. You will need the onsft API reference to fill it in. Keep in mind that Make states its onsft documentation is limited for lack of public information, so test every call with Run once and read the returned bundle before you switch the scenario on.
05Should you use Make or n8n for onsft?
It depends on the tool your team already works in. On Make, onsft offers six modules: create, get, update, delete, search, plus a generic API call, all usable from the Free plan. Apps listed in Make often have an n8n node too, but this page does not confirm one for onsft, so check the n8n node list before you decide. If both exist, compare them on what you actually need: the operations available, how each tool counts usage and which editor your team finds easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations