Easily set up automated processes called Zaps that connect Slite with popular apps like Google Sheets, Slack, Asana, Google Docs, and more. No coding required.
How the Zapier integration works
Pick a Zap workflow from the available templates or create your own, then follow the prompts to authorize your Slite account and set up automations between Slite and thousands of other apps.
Setting up a Zap from an available template
Setting up a Zap from scratch
Set up a trigger to start your Zap (e.g. a new TypeForm entry)
Select the Slite app to perform the action
Select from one of the following events:
- Create Doc
- Fetch Doc
- Fetch Sub Docs
- Replace Doc
- Search Docs
- Update Doc
- Ask Question (Learn more: Ask )
To see a detailed list of the events along with the corresponding parameters, visit this section of the Zapier guide .
Getting the parent doc id
The doc id will look something like this:
GcKO7QlX4fzVM9To get it:
Click the 3-dot menu in the top-right corner of the doc
Choose
Copy doc id
If the parent doc id is already set with a default template, it will not take the markdown to fill the doc created but the template.
Getting the block id
The block id will look something like this:
5374311c-2bc1-48ed-b689-7b6e4d7a9923To get it:
Navigate to the doc you want to update
Hover over the beginning of a line
Click the four-dot menu
Choose
Copy block id
Trigger vs Action
Currently, our Zapier implementation does not offer a
trigger. This means you can act on your Slite data based on 3rd party events, but not have a workflow triggered by an action in Slite.
