Resources · Make integration

Softr Make integrationAutomate Softr with Make.

Can your Softr app update itself when its data changes? The Softr Make integration gives you 11 modules: 2 triggers that watch database records, 8 actions and 1 search. This guide is for teams running a client portal or internal tool, and it walks you through your first working scenario.

Try the Softr integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Softr Make integration do for you?

The Softr Make integration links your Softr account to Make, a visual automation tool, so your records and users can move without anyone copying data by hand. Make watches your Softr databases, reacts when a record appears or changes, and then creates, updates or removes records and users for you.

Portal access that follows your data. A client fills a form and a row lands in your Softr database. Database Record Added picks it up and Create a User gives that client a login to your portal, so nobody on the team has to open the Softr dashboard.

Records that stay in sync. When a status changes in one tool, Find Database Record locates the matching Softr row and Update Database Record writes the new value. The search comes first because it can return several rows, and you only want to touch the right one.

Clean offboarding. When a contract ends, Delete a User removes the person from your Softr domain. Pair it with Delete Database Record if the row should go too, knowing that a deletion cannot be undone from Make.

Keep the limits in mind: both Softr triggers are scheduled, so Make checks for changes on the scenario's schedule instead of hearing from Softr the moment something happens. If you want to weigh this against a code-friendly option, read n8n vs Make, and for a wider view of the platform see our Make review. Stuck on an error later? Make troubleshooting covers the common cases.

Connect

How do you connect your Softr account to Make?

  1. 01

    Generate your Softr API key

    Log in to Softr and open the Dashboard. In the top right corner, click your profile icon, then API key, and press Generate API key. Copy the value and keep it somewhere safe, since Make will ask for it next.

  2. 02

    Open a Softr module in Make

    In your Make scenario, add any Softr module and click Create a connection. A connection is your Softr account linked to Make once, then reused by every Softr module. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the key into the API Key field and click Save. If Softr asks you to authenticate or confirm access, accept it. The connection now appears in the module, and Make can list the databases it is able to read.

First scenario

Build your first Softr scenario in Make

GoalWhen a new record is added to your Softr database, Make creates a matching user so the person can sign in to your portal.

  1. 01

    Create the scenario

    Go to the Scenarios page and create a new scenario. A scenario is the automation you build: a chain of modules. Click the big + to place the first one.

  2. 02

    Add the trigger

    Search for Softr, choose Database Record Added and select your connection. Pick the database where new sign-up requests land; once connected, Make shows you what it can read.

  3. 03

    Add the user action

    Click the + on the right of the trigger and add Create a User. Map the values coming from the new record into the module, so each bundle, meaning one record, becomes one user.

  4. 04

    Test with Run once

    Add a test record in Softr, then click Run once. Open the bubble above each module to read the bundle it received and check that the user was created as expected.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, which is every 15 minutes by default, then switch the scenario on. From here, Make checks your database on that rhythm.

Triggers

Softr triggers: what starts your scenario

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

Softr1Database Record Added

Database Record Added

Scheduled trigger

In Make“Triggers when a new record is added in a database.”

This trigger starts your scenario each time a fresh record shows up in the Softr database you select, so new form entries, requests or orders get handled without anyone watching the table. Every new record reaches the next module as its own bundle.

How it fires
scheduled. Make checks Softr on the scenario's schedule, so a record waits until the next check before it is picked up.
When to use it
a client portal where each new request should open a user account or notify your team.
Watch out
on the Free plan, checks can't run closer than 15 minutes apart, so plan for that delay.
Softr2Database Record Updated

Database Record Updated

Scheduled trigger

In Make“Triggers when a record in a selected database is updated.”

Reach for this one when edits matter more than additions: it wakes your scenario whenever an existing record in the chosen database is changed, which lets you react to a status flip, an approval or a corrected detail.

How it fires
scheduled. Make checks Softr on the scenario's schedule rather than being alerted by Softr, so changes are collected at each check.
When to use it
a project tracker where moving a row to “Approved” should update another tool or remove access.
Watch out
if your scenario later writes to that same database with Update Database Record, filter carefully, or its own edits will fire it again.
Modules

Softr modules: what Make can do in your account

Softr gives you 9 modules in 3 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

7 modules
Softr1

Create a User

Action

In Make“Adds a new user to your Softr.io domain.”

Gives someone a login to your Softr domain straight from Make, so new clients or teammates get portal access the moment their data is ready. Each bundle it receives turns into one user.

When to use it
right after a signed deal or an approved request, to open access without touching the Softr dashboard.
Watch out
map the values carefully, since a test run creates a real user.
Softr2

Create Database User

ActionIn the docs only

Appears in the Softr documentation under its name alone, with no official description of what it does or what it returns. Treat it as a module to explore: drop it into a test scenario, fill what Make shows you and read the result before any real use.

When to use it
only after Create a User has proved it doesn't fit how your app handles its users.
Watch out
run it once on test data and read the bundle, since nothing documented tells you the outcome in advance.
Softr3

Delete a User

Action

In Make“Deletes a user from your Softr.io domain.”

Removes a person from your Softr domain, which is how you close portal access cleanly when a contract ends or someone leaves. It pairs naturally with an update trigger that spots the end of a relationship.

When to use it
offboarding a client or a contractor as soon as their record says they are gone.
Watch out
the deletion cannot be undone from Make, so place a filter in front of it and test on a dummy user first.
Softr4

Delete Database Record

Action

In Make“Deletes a record in a database”

Erases one record from a Softr database, keeping your tables free of duplicates, test rows or entries that no longer belong there. It acts on a single record per bundle.

When to use it
after Find Database Record has located a row you know should disappear, such as a cancelled request.
Watch out
Make has no undo for this, so make sure the search returned the exact row before the delete runs.
Softr5

Make Application API Call

Action

In Make“Use REST API to perform actions.”

Opens the door to the Softr REST API for actions on your application that the ready-made modules don't cover. You describe the request yourself, and Make sends it with your existing connection.

When to use it
once you have checked every other Softr module and still miss an application-level action.
Watch out
this module expects you to know the Softr API, so it is the least beginner-friendly brick on this page.
Softr6

Make Database API Call

Action

In Make“Make Database API Call”

Sends a custom request to the database side of Softr, a fallback for record operations the dedicated modules don't handle. It reuses your connection, so there is no second key to manage.

When to use it
when Find, Create, Update and Delete Database Record together still can't express what you need.
Watch out
start with the dedicated database modules, which are easier to read and to fix when something breaks.
Softr7

Update Database Record

Action

In Make“Updates a database record.”

Changes the values of an existing Softr record, which keeps a status, an owner or a note current without anyone editing the table. You point it at one record and send only what should change.

When to use it
when an event in another tool, like a paid invoice, should move a Softr row forward.
Watch out
if Database Record Updated watches the same database, this edit can start that other scenario, so add a filter.

Searches

1 module
Softr8

Find Database Record

Search

In Make“Find record(s) in a table”

Looks up records in a Softr table and hands them to the next module, which is how you get the right record before updating or deleting it. Unlike an action, a search can return zero, one or several bundles.

When to use it
any time you know something about a record but not which row it is.
Watch out
when several rows match, each one flows on and the next module runs once per row, costing operations.

Other modules

1 module
Softr9

Create Database Record

Action

In Make“Creates a record in a database.”

Adds a new record to a Softr database from data arriving in Make, so information collected elsewhere shows up in your app without retyping. Each bundle becomes one row.

When to use it
feeding a Softr directory or tracker from a form, a CRM or a spreadsheet handled by another module.
Watch out
if Database Record Added watches that same database, each new row will start that trigger too.
Need help

Need help automating Softr with Make?

A person reads every message.

FAQ

Softr and Make: frequent questions

01Is the Softr Make integration free?
Yes. Softr is a standard app in Make, available from the Free plan, so you can connect it without paying for Make. The Free plan does come with limits: 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 lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage on every plan is counted in operations, one per module per bundle, so busy databases consume more of your monthly allowance.
02What do you need to connect Softr to Make?
You need a Softr account and a Make account. In Softr, open the Dashboard, click your profile icon in the top right corner, choose API key and click Generate API key, then copy the value. In Make, add any Softr module, click Create a connection, optionally give it a name, paste the key into the API Key field and click Save. If Softr asks you to authenticate or confirm access, accept it. That single connection is then reused by all 11 Softr modules in your scenarios.
03Does the Softr trigger fire instantly in Make?
No. Both Softr triggers, Database Record Added and Database Record Updated, are scheduled triggers. Make checks your Softr database on the scenario's schedule instead of receiving an alert from Softr, and a new scenario is set to every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap allowed between two scheduled runs, while paid plans can go down to 1 minute. Records that change between two checks are all picked up at the next one, each as its own bundle.
04What if a Softr module you need is missing in Make?
It depends on what is missing. Softr does not have the generic Make an API Call module, but it offers two of its own escape hatches: Make Application API Call and Make Database API Call, which send custom requests to the Softr REST API through your existing connection. They require some knowledge of that API. If the gap is outside Softr, another app in Make may cover it, since more than 3,000 standard apps are available on every plan. And if you would rather not build it yourself, the team can help.
05Should you use Make or n8n for Softr?
It depends on how you like to work. Make offers Softr as a standard app with 11 ready-made modules, two scheduled triggers and a guided editor where you test each step with Run once, which suits people who want to connect their portal without writing code. The same app often has a node in n8n as well, so both tools can usually reach your Softr data. The fair way to decide is to list the modules your case needs, check that each tool covers them and try the one whose editor feels natural to you.
Same platform

Other docs you might need on this stack.

Browse all integrations