Integrations

Connect conversations to approved business actions

Give the agent narrow, explicit tools instead of broad access. Start with read checks and structured outputs, then add confirmed write actions where they are justified.

12 detailed topics English content

Integrations

An integration should make the next step clearer

Telp tools have an explicit description, input contract and permission policy. Credentials stay on the server, while operators can see what was attempted and where a workflow needs attention.

Explicit inputs

The agent collects structured fields instead of sending an uncontrolled conversation blob.

Controlled actions

Read checks, drafts and write actions can have different confirmation requirements.

Visible failures

A failed integration remains visible for review instead of silently pretending the action worked.

Explore details

All Integrations topics

Automation

AI agents with Zapier, Make and n8n automations

Send structured conversation outcomes to Zapier, Make, n8n, Pipedream, Airtable or similar workflow tools.

Explore details

Customer data

CRM and help desk systems for AI agents

Prepare or update customer records in systems such as HubSpot, Pipedrive, Salesforce, Zendesk or Intercom through approved connections.

Explore details

Commerce

AI agents for WooCommerce, Shopify and Wix

Use native catalog and order capabilities for supported WooCommerce and Wix stores while keeping business rules in Telp.

Explore details

Back office

Google Workspace workflows for AI agents

Use Google Sheets, Gmail or controlled email delivery as a practical operational output for smaller teams.

Explore details

Developer

REST tools and webhook connections for AI agents

Connect internal systems through explicitly configured HTTP endpoints and structured input contracts.

Explore details

Advanced

MCP and custom tools for AI agents

Expose specialized operations when the business logic and authorization should remain owned by your server.

Explore details

Connections

AI agent for WordPress / WooCommerce

An AI agent uses the connected WooCommerce catalog on your WordPress website to answer product questions, check variants and prepare supported ordering.

Explore details

Connections

AI agent for Shopify stores

An AI agent checks Shopify products and options from a connected source. Checkout needs separate authorization and a supported channel; the public catalog is read-only.

Explore details

Connections

AI agent for Wix stores

An AI agent checks your connected Wix range, answers product questions and prepares the next step within the supported store actions.

Explore details

Connections

AI agent with Zapier automations

An AI agent collects agreed conversation details and prepares them for a configured Zapier automation in your business tools.

Explore details

Connections

AI agent with Make automations

An AI agent collects a business enquiry and passes the details to your Make scenario through an approved connection for the next step.

Explore details

Connections

AI agent with n8n workflows

An AI agent collects the required details and sends them to your configured n8n workflow within its authorized actions.

Explore details

Integrations

Choose the simplest reliable connection

Automation platforms are useful for a fast pilot. Native or direct server integrations fit flows that need stronger identity, authorization, product context or lifecycle control.

  • What data the agent needs to read
  • Which actions change business state
  • Who must confirm sensitive writes
  • How failures reach the responsible team

FAQ

Questions before you choose

What can an integration let the AI agent do beyond answering questions?

A connected system can enable product search, status checks, recording a sales contact, opening a support request or making a reservation. The agent receives only agreed actions; a connection does not imply unrestricted access to all data.

How does a dedicated connection differ from a Zapier, Make or n8n workflow?

A dedicated connection covers specific supported actions in a particular system, such as a store catalog. Zapier, Make and n8n connect steps that you configure separately. An app appearing in their catalog does not mean it is immediately ready for every task in Telp.

Can a write action or order require confirmation before execution?

Yes. For actions that require confirmation, the agent prepares the details first and execution waits for the appropriate confirmation. During a voice conversation, spoken approval does not replace written confirmation when it is required.

What does the customer see if a connected system does not complete an action?

They do not receive a false confirmation that the job is finished. The agent gives an understandable next step, and the team can investigate and take over the request. Starting an automation and completing the job are different outcomes.

Not sure where to start?

Share the channels you use and the customer work that repeats most often. We will suggest one focused first workflow.