Make Integration

Please note: Make.com is a separate, 3rd party, tool that requires its own subscription and has separate fees from your Knack subscription.

What You'll Learn

This overview will help you understand how to leverage Make's powerful automation capabilities with your Knack app. You'll discover how to set up scenarios that connect Knack to hundreds of other services, configure triggers that respond to record changes in your live app, and create actions that automatically update records or upload files. Whether you're looking to streamline workflows by connecting Knack to Google Sheets, Slack, or Dropbox, or you want to automate complex business processes, this integration provides robust automation possibilities for enhancing your app's functionality.

Tip: All Knack customers have access to Knack's native integration and automation feature, Knack Flows. For more details on Flows, please visit our documentation or start building your first flow within an app.

What You Can Do with Make Integration

Need to send a Slack message when a new record is created in Knack? No problem. You can even move data into your Knack app. For example, you can create a new record in Knack when a new bank transfer is added in Xero.

Available Service Connections

Make offers integrations to hundreds of other services. Some popular services to connect Knack with include:

• Google Sheets

• Slack

• Mailchimp

• Twilio

• Dropbox

• Xero

• You can find and search the full list of available services on Make's website .

How Make Works

Make uses scenarios composed of modules to connect different services. Each scenario watches for a trigger that will initiate the scenario. Once the scenario is triggered, it can perform a series of actions.

For example, a new form submission in Knack can trigger the action to send a Slack message.

Available Triggers and Actions

Available Triggers

• Watch records: Triggered when a new record is created, updated, or deleted

• New events: Triggers when a new record is added

  Note: These triggers only work with records created, updated, and deleted in your Live App. These triggers will not be initiated by records created, updated, or deleted in the Builder.

  Important: In Knack's native "Flows" feature, triggers work in 1) the Live App, 2) the API, and 3) the Builder area for single-operations. Flows do not trigger from bulk-updates in the Builder or record updates from the Scheduled Task feature.

Unavailable Triggers

• Records created on a table (via the Builder or with the API)
• Records created via form record rules
• Records created via "insert connected record" on an action link

Available Actions

• Create Record: Creates a new record

• Delete Record: Delete a record specified by its ID

• Get a Record: Returns details about a record specified by its ID

• Update Record: Updates a record

• Upload a File: Uploads a file or image

• Make an API Call: Performs an authorized API call

• Search for Records: Searches for a record

  Note: When using the "Make an API Call" action, instead of using a full URL like Postman expects (e.g., https://api.knack.com/v1/objects/object_xx/records), this particular action requires a simplified URL: /v1/objects/object_1/records.

Connecting Make with Knack

You will first need to sign up for a Make account before you can set up an integration with Make.

When setting up a scenario in Make, add Knack, and then you will be able to set up a connection to your specific Knack app by using the application ID and the API key:

You will be prompted to name your connection. You can find the Application ID and API key in the API & Code section of the App Settings while in your Builder:

Important Notes for Special Configurations

• Private server customers: You will need to use the "Show advanced settings" checkbox option to add your custom private server domain

• HIPAA customers: You'll need to use the endpoint of http://usgc-api.knack.com/

• HIPAA compliance: Using Make with a HIPAA app is not compliant unless you're able to sign a BAA (Business Associate Agreement) with Make

  Copy the Application ID and API key and paste them into the corresponding fields in the Make form and select "Continue". You will then see your Knack connection in the list of available Knack accounts.

Working with Fields

Knack uses very specific field types to ensure maximum utility within your app. Field types tell Knack what type of data is stored in a field and how to use it.

Some of these fields have multiple components, like person and address fields. For example, a person field can be split into first and last names.

When using Knack as a trigger, you can choose to use the formatted value of these fields, or you can use the individual components. When using a Scenario to create a new Knack record, you'll have to fill in the individual components for these fields to ensure they are added to your app correctly.

For example, the "First" and "Last" names of a person field can be used when submitting to a service requiring separate name fields. If you need to submit a full name to a connected service, you can combine these fields.

When using the full field, it will follow the formatting parameters you've set for that field. For example, if your person field uses the format "Last, First, Middle", then your trigger should submit the name in that order.

Files and Images

Files and images can be uploaded into Knack using the "Upload a File" action.

For example, this can be used with a service like Dropbox to store your images and files and upload them into your Knack app. The files will need to be mapped directly using the file name and data.

Field Type Limitations

Timer Fields

Timer fields are not available with the Make integration due to their from/to formatting.

Signature Fields

Signature fields (.svg format) are not available with the Make integration.