A connector lets Automize talk directly to another application's API – Slack, Airtable, a banking system, an HTTP endpoint, and many more. Connectors are how Cloud processes get work done without a bot, and they can be used in bot processes too.
1. Add a connector step
- On the process map, open the Add panel. Connector actions are grouped by app.
- Drag the action you want onto the canvas (for example "Send message" for Slack, or "Create record" for Airtable).
- Open the step to configure it. Pick the specific action, and the step's input fields appear automatically based on what that action needs.
- Choose the connection (the saved credential) the step should authenticate with.
- Fill in the action's fields. You can type fixed values or insert variables.
2. Test a connection
On the connector's settings page, after entering the credential details, use the Test button to check it works before you rely on it:
- If something is missing, Automize tells you which fields are still required.
- For connectors that support a live check, it makes a real authenticated call and reports the result – for example "Connected – the connector accepted the credential", or "The connector rejected the credential. Check the saved key or token."
- Some connectors (such as OAuth ones) are verified when you authorise them rather than from the Test button.
3. Pass data between steps
A connector step produces output that later steps can use. Reference an earlier step's output, or an input the flow was started with, using template expressions in a field – for example {{steps.<step>.output.<field>}} or {{inputs.<field>}}. This is how you wire the result of one call into the next.
4. Good to know
- Automize ships with a large library of connectors, plus a general HTTP request connector for any API that isn't covered yet.
- Browse the Connectors collection in the help centre for app-specific guides.