Integrations · Preview

Connected action

SystemBusiness calendar

OperationRead available times

ResponseAvailable slots

Bring the right information into the task.

Integrations.
Your systems, connected.

Bring the right information into the task.

Connect the tools your team works with. Use supported connections and APIs to read information, take an approved action and return the result.

Talk to sales

Integrations capabilities.

Supported connections

Link a system available in your setup. Reduce manual movement between tools. Authorize the account with the required permissions and map its identifiers.

For a compatible calendar, CRM or business application.

How it works +

Select a connection and check which operations are supported in your setup.
Authorize the account with the required permissions and map its identifiers.
Run a controlled lookup or update to confirm the workflow receives the expected result.

Custom API actions

Use an accessible API for a specific operation. Connect tasks to internal or specialized tools. Configure authentication securely and keep credentials out of prompts and caller-visible content.

For a system that needs a custom connection.

How it works +

Define the endpoint, method, required inputs, and expected response fields.
Configure authentication securely and keep credentials out of prompts and caller-visible content.
Validate successful, empty, and unsuccessful responses before enabling the action.

Data mapping

Define what the workflow sends and receives. Keep the task connected to the correct record. Validate required values and distinguish a missing record from an unsuccessful lookup.

For lookups, confirmed updates and returned outcomes.

How it works +

Map caller details to the identifiers and fields expected by the connected system.
Validate required values and distinguish a missing record from an unsuccessful lookup.
Confirm updates from the response and define how repeated requests should be handled.

Connect the system
that owns the task.

Calendars

Read availability or submit an approved booking operation.

Customer records

Find the right account and update permitted fields.

Internal applications

Expose a defined operation through a suitable API.

Connect with purpose.
Verify the whole path.

Check whether a supported integration covers the required operation or whether a custom API action is needed.

Integrations / ConfigurationPREVIEW

Define the essentials.

Setting 01Source system

Setting 02Supported operation

Setting 03Connection method

A clear scope for each step

Explore documentation →

Configure access and the required fields. Define a response the agent can use and a path for errors.

Integrations / LogicPREVIEW

STARTAuthorization

PROCESSRequired inputs

EXPECTED RESULT

Continue

NEEDS ATTENTION

Review

Explore documentation →

Test the action in a controlled environment and check the record in the connected system.

Integrations / ReviewPREVIEW

Review the complete path.

Check 01Known input

Check 02Actual system response

Check 03Failure or duplicate

Verify before approving the result

Explore documentation →

Connect everything.
Work seamlessly.

Integrations.
Your questions, answered.

Talk to our team

Does a listed integration support every action in that product?+

No. Treat the directory as a starting point for review. Confirm the exact objects, read and write actions, authentication method, and account requirements your workflow needs.

Can we connect an internal system with an API?+

Share its API documentation, authentication requirements, and expected actions for a technical review. Network access, permissions, and response times determine the integration work needed.

How do we prevent duplicate bookings or record updates?+

Design the integration around stable identifiers, action confirmation, and duplicate protection where the destination supports it. Test retries and timeouts and verify the final record rather than assuming the first request succeeded.

What should the agent do when a system returns no result?+

Define a clear fallback for missing records, expired credentials, and service failures. The agent should explain the verified state and offer a handoff or follow-up instead of inventing a result.

What needs to be ready for an integration pilot?+

Provide a test account, scoped credentials, representative records, a named system owner, and expected success and failure responses. Confirm which production permissions will be needed after validation.