Skip to main content
Use Make to connect your Zite database to another app. A scenario runs a sequence of modules. You connect Zite with your API key and webhooks. For example, another tool can create a record in your Enquiries table. Or a published Zite app can send a completed request to the next step in Make.
Zapier has a ready-made Zite app with one-click sign-in. With Make, you connect using your API key and webhooks.

​
Create a scenario

1

Get your API key

Set up the connection using an API key from Zite’s Developer settings. The key is visible to admins only. Keep it private.Open Settings, then Developer, then the API key tab. If you see the Zite REST API empty state, click Enable API. Then click Copy.There is one key per organization. Regenerate replaces the key everywhere, so anything using the old key stops working. Only share the key with tools you trust.
2

Read or change records

In a Make scenario, use Make’s HTTP module with your API key to read, create, update, and delete records (up to 100 at a time). You can also list records with filters and sorting.See Zite’s developer documentation for the exact settings to put in the HTTP module.
3

Send data with webhooks

To send data from Make into a Zite app, open Workflows, then Webhooks, and click Add webhook. Describe what should happen in the chat. The Zite agent builds it. Copy the webhook’s Inbound URL. In Make, add an HTTP module that sends your data to that URL. The app must be published.To send data from Zite to Make, start a scenario with a Custom webhook and copy its address. In your Zite app, ask the Zite agent to add a step to a workflow that sends the data you want to that address. There is no ready-made step or guided setup for this yet.
4

Test the connection

Run the scenario with sample data. Check the new or updated record in Zite, or the incoming data in Make, before you enable the scenario.If a scenario loops over lots of records, add a short delay with Make’s Sleep module between steps. Zite allows 30 requests per second per database.

​
Choose what to connect

Anyone with a Zite webhook URL can trigger it, so keep it private. You can Rotate it to get a new URL, or use the Pause switch. Data can be up to 1 MB.

​
If a scenario doesn’t work

  • Records don’t change: Check that you copied the current API key and that it hasn’t been regenerated.
  • The Zite app doesn’t react: Confirm the app is published, the webhook is not paused, and Make is sending to the current Inbound URL.
  • A run fails after many records: Add a short delay with Make’s Sleep module so the scenario stays under 30 requests per second per database.
Need help? Contact support@zite.com.
Last modified on October 27, 2026