Custom IntegrationsBETA
These features are available in the beta version. Try them out and share your feedback — it helps us improve the product.
Integrations are the process of combining different systems and applications to enable data and functionality exchange.
Integrations help automate workflows, reduce manual effort, speed up tasks, and lower the risk of errors. For example, integrating with Jira allows you to automatically create issues when new emails arrive or change issue status based on specific conditions.
To work with integrations, follow these steps:
- Add an integration to your workspace.
- Configure the connection by entering your credentials for the selected service.
- Create scripts with integration blocks.
Adding an Integration to a Workspace
To add an integration to a workspace:
- In the workspace Control Panel, click + Add and select Integration.
- In the pop-up window, provide the following:
- Integration name
- Logo — upload an icon of the integrated system in .svg or .png format
- Description (optional)
- Click Create.
After adding the integration, the code editor will open automatically where you can write the integration logic.
Configuring the Connection
Once the integration its code is added, configure the connection and sign in using your credentials to ensure the integration works properly. Required fields may vary depending on the connection type.
Connection types:
- OAuth2 — uses a token instead of login/password. Tokens provide access without re-entering credentials. Requires a client ID and secret. Used for Google Drive, Google Sheets, Microsoft SharePoint, amoCRM, and others.
- Login and Password — simply enter your credentials. Used for integrations with Jira.
- API Key — an API key is a unique code allowing access without login/password. Requires a generated key and script editing rights. Suitable for integrations with Huntflow and Operavix.
The instruction for adding a connection is available in Control Panel.
Using Integration Blocks in Scripts
Once an integration is added to a workspace, its blocks become available in scripts.
To use them:
- Create a script and add a trigger block.
- Add the next block and select the Installed block category.
- Select the integration to view all available blocks and choose the desired one.
- Enter parameters or use mapping, then test the block.
After testing, the block returns data based on the inputs.
Was the article helpful?