Resources · Make integration

Knack Make integrationAutomate Knack with Make.

Can Make keep your Knack records moving without code? Yes. The Knack Make integration gives you 9 modules, 2 of them triggers. This guide is for teams who run their database on Knack: it shows how to link your account and build a first scenario.

Try the Knack integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Knack Make integration do?

The Knack Make integration links your Knack app to Make, a visual automation tool. You build a scenario, the automation itself, as a chain of modules. Each module is one brick: something that starts the flow, an action on a record, or a search. Records then travel between Knack and your other apps with no copy and paste.

React to every form submission. New Event fires as soon as someone submits a Knack form or a record is created, updated or deleted. The next module, from another app, can alert the right person or copy the data where it belongs.

Keep related records in step. Watch Records spots each new record, Search for Records finds the entries tied to it, and Update a Record changes them. That is the first scenario built further down this page.

Feed Knack from your other tools. When a lead lands in your CRM, Create a Record adds it to Knack, and Upload a File sends the matching document or image along.

The Knack documentation gives no numeric limit for these modules. When an action is missing, Make an API Call reaches the rest of the Knack API with the same connection. Knack may also exist as an n8n node; the n8n vs Make comparison helps you pick. New to the editor? The Make training starts from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect Knack to Make?

  1. 01

    Copy your Knack keys

    Log in to Knack and open Settings, then Apps. In My Apps, click App Builder next to your app and go to Settings, API & Code. Copy the Application ID and the API key and keep them somewhere safe.

  2. 02

    Add a connection in Make

    Drop any Knack module into your scenario and click Add next to the Connection field. A connection is your Knack account linked to Make once, then reused by every Knack module. A label in Connection name is optional.

  3. 03

    Paste the keys and save

    Paste both values into the Application ID and API Key fields. Fill Private API server domain only if your Knack account sits on a private server. Click Save: every Knack module can now use this connection.

First scenario

Build your first scenario with Knack

GoalWhen a new record is added in Knack, Make finds the related records and updates them.

  1. 01

    Create the scenario

    Open the Scenarios page in Make, create a new scenario and click the + to add the first module. Type Knack in the search box and pick Watch Records.

  2. 02

    Connect and set the trigger

    Click Create a connection and paste your two keys. Once the link works, fill the module fields: Make lists what it can read in your Knack app, so you pick where new records should start the flow.

  3. 03

    Add the search

    Click the + on the right of Watch Records and add Search for Records. Map a value from the new record to find the entries tied to it. A search can return zero, one or several bundles, the items passed to the next module.

  4. 04

    Update what you found

    Add Update a Record after the search and map the ID of each record it returned. Fill only the values that should change. Each bundle gives one update, and each update counts as one operation on your plan.

  5. 05

    Test with Run once

    Add a test record in Knack, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check that the right records changed.

  6. 06

    Schedule and switch on

    Watch Records is a scheduled trigger: Make checks Knack on the scenario schedule, every 15 minutes by default. Set the interval on the first module, then switch the scenario on.

Triggers

What can start a Knack scenario?

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

Knack1New Event

New Event

Instant trigger

In Make“Triggers when a new record is created, updated or deleted or when a form is submitted.”

New Event hands you each change in your Knack app the moment it happens: a record created, updated or deleted, or a form submitted. One trigger covers all four cases, which makes it the natural starting point for anything urgent.

How it fires
instant. Knack calls Make through a webhook as soon as the event happens, with no schedule to wait for.
When to use it
a public form on your Knack app collects support requests, and each one should reach the right person right away.
Watch out
updates and deletions fire it too. If your scenario writes back into the same Knack app, it may start itself again.
Knack2Watch Records

Watch Records

Scheduled trigger

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

Watch Records gives you every record newly added to Knack, one bundle per record, ready for the next modules. It looks at additions only, not at edits.

How it fires
scheduled. Make checks Knack on the scenario schedule, every 15 minutes by default, and 15 minutes is also the shortest interval on the Free plan.
When to use it
new orders or sign-ups land in a Knack table and a short delay is fine before the follow-up runs.
Watch out
changes to existing records never reach it. For those, pick New Event instead.
Modules

What can Make do in Knack?

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

Actions

6 modules
Knack1

Create a Record

Action

In Make“Creates a new record.”

Create a Record adds a fresh entry to Knack from data coming out of another module, so nobody retypes it. You map each incoming value onto the Knack field that should hold it.

When to use it
a lead captured by a form tool or a paid order in your shop should become a Knack record straight away.
Watch out
if New Event watches the same app, the new record fires it too, so check that this chain is intended.
Knack2

Delete a Record

Action

In Make“Deletes a record specified by its ID.”

With Delete a Record, a Knack entry picked by its ID disappears as part of the flow. Your tables stay clean when the source item no longer exists anywhere else.

When to use it
a customer cancels in your billing tool and the matching Knack record has to go.
Watch out
a deletion cannot be undone from Make. Run once on a dummy record before you switch the scenario on.
Knack3

Get a Record

Action

In Make“Returns details about a record specified by its ID.”

Need the full content of one record? Get a Record reads it by its ID and passes every value to the next module, so later steps can use any of them.

When to use it
an earlier step or another app gave you only the ID, and you need the rest of the record to write an email or a report.
Watch out
it needs an exact ID. If you only know a name or an email address, start with Search for Records.
Knack4

Update a Record

Action

In Make“Updates a record specified by its ID.”

Update a Record changes an existing Knack entry, found by its ID, with fresh values from your scenario. You fill in the values that should change and leave the rest alone.

When to use it
a payment is confirmed in another app and the matching Knack record should show it.
Watch out
map the ID from Search for Records or from a trigger. A typed ID edits the same record on every run.
Knack5

Upload a File

Action

In Make“Uploads a file or image.”

Upload a File puts a file or an image from your scenario into Knack, for example a signed PDF from your e-signature tool or a photo sent through a form.

When to use it
documents arrive by email or in cloud storage and belong next to your Knack data.
Watch out
on the Free plan, Make handles files up to 5 MB. Check the size of large scans before you build around them.
Knack6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is your way out when the listed modules stop short: it calls any endpoint of the Knack API with the connection you already set up, no second login needed.

When to use it
you need an action that none of the other Knack modules covers.
Watch out
you write the request yourself, so keep the Knack API documentation open next to the module while you build it.

Searches

1 module
Knack7

Search for Records

Search

In Make“Searches for a record.”

Search for Records finds the Knack entries that match what you look for and returns them to the scenario. It is how you get an ID when you only know a name or an email.

When to use it
before an update or a deletion, to locate the right record from data sent by another app.
Watch out
the result can be zero, one or several bundles. Every following module runs once per bundle, so a loose search can change more records than planned.
Need help

Need help automating Knack with Make?

A person reads every message.

FAQ

Questions about Knack and Make

01Is the Knack Make integration free?
Yes. Knack is a standard app in Make, so it works on the Free plan. That plan keeps 2 scenarios active, runs scheduled triggers at most every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB, with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) go down to a 1 minute interval and allow unlimited active scenarios. Your Knack subscription is a separate question that this page does not cover.
02What do you need to connect Knack to Make?
A Knack account and two values taken from it. In Knack, open Settings, then Apps, click App Builder next to your app and copy the Application ID and the API key from Settings, API & Code. In Make, click Add next to the Connection field of any Knack module and paste both. The documentation lists no other prerequisite. The Private API server domain field only needs a value if your Knack app runs on a private server.
03Does the Knack trigger in Make work in real time?
It depends on the trigger. New Event is instant: Knack calls Make through a webhook when a record is created, updated or deleted, or when a form is submitted, so the scenario starts right away. Watch Records is scheduled: Make checks for new records on the scenario schedule, every 15 minutes by default and never more often than that on the Free plan. Paid plans go down to 1 minute. Pick New Event when a delay would hurt.
04What if a Knack module is missing in Make?
Use Make an API Call. It sends any request to the Knack API with the same connection as the other modules, so there is no second account link to set up. The other modules already cover the everyday work: creating, reading, updating, deleting and searching records, plus uploading files or images. The Knack documentation on Make gives no numeric limit for them. If a request still fails, the error shown after Run once is the first place to look.
05Make or n8n for Knack?
It depends on where your other automations already live. In Make, Knack comes with 9 modules, including an instant trigger, a search and Make an API Call, all available on the Free plan. The same app often exists as an n8n node as well, and this page does not rank the two. Check whether the listed modules cover your case and which tool your team already knows. The comparison page linked earlier on this page sets out the differences.
Same platform

Other docs you might need on this stack.

Browse all integrations