Extend Your App
      Back to home
      1. Knowledge Base
      2. Extend Your App

      Integrate with Make

      Unlocking Efficiency: A guide to seamlessly integrating Knack with Make, exploring available functionality, triggers, and actions.

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

      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. 

      This article covers the following topics:

       

      What is Make?

      Make is a third-party automation tool that allows you to connect Knack to other third-party services. With Make, you build simple automation for repetitive tasks that move your data from one app to another or trigger events in other apps automatically.

      What can you do with a 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. 

      What services are available to connect with?

      Make offers integrations to hundreds of other services. You can find and search this list of services to connect with.

      Some popular services to connect Knack with are:

      • Google Sheets

      • Slack

      • Mailchimp

      • Twilio

      • Dropbox

      • Xero

       

      How does Make work?

      Make use of 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. 

       

      What Knack triggers and actions are available? 

      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.

      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, for example, https://api.knack.com/v1/objects/object_xx/records , this particular action requires a simplified URL: /v1/objects/object_1/records.

       

      How to connect Make with Knack

      Note: 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 these in the API & Code section of the App Settings while in your Builder (see image below). 

      Notes:

      • If you are a private server or a HIPAA customer, you will also need to use the "Show advanced settings" checkbox option seen in the image above to add your custom private server domain. 
      • When on a HIPAA plan, you'll need to use the endpoint of http://usgc-api.knack.com/.
      • Using Make with a HIPAA app is not compliant unless you're able to sign a BAA (Business Associate Agreement) with Make.
      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. 

      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.