Call any HTTP API as a workflow step, with mapped inputs and outputs.
REST API
Counts describe the planned connector design, not shipped functionality.
Overview
The generic connector for systems without a dedicated integration: define a request, map fields from earlier steps and use the response in later rules.
REST API is planned, not yet available
Scheduled poll
Call an endpoint on a schedule and react to changes
HTTP request
GET, POST, PUT, PATCH or DELETE with mapped fields
Parse response
Use response fields in later steps
Authentication concept
Credentials would be attached to a connection and stored as managed secrets, never inline in the workflow definition.
Secrets handling is described on the security page.
Connection status
Authorize
Choose scopes and grant access
Test
Send a sample request from the workflow builder
Use
Reference the connection from any workflow
Illustrative connection flow. It becomes available with the integration.
Example workflow
Extract invoice fields with AI, validate against rules, approve when required and post to accounting.
Related
Invoice Processing
Extract invoice fields with AI, validate against rules, approve when required and post to accounting.
Support Routing
Classify incoming requests with AI, set priority by rule and assign them to the right queue.
Expense Approval
Extract receipt details, check policy limits, route approvals and record approved expenses.