Skip to main content

Connected-app tools

Turn an action of a connected app, such as creating a Google Calendar event or saving a CRM lead, into a tool an agent can use.

What you will achieve

An agent will be able to use an app you connected, for example to book a Calendly slot or post to Slack, with no endpoint to build.

Prerequisites

  • The app connected on Integrations (see Integrations overview).
  • The app must be one that offers agent actions. Every app on the Integrations page does (see the table below).

Step-by-step setup

  1. Open the agent, Tools tab, Your tools, Add tool.
  2. Choose Integration.
  3. Under App, pick a connected app. Under What the agent can do with it, pick an Action.
  4. Review the Name, Description and Run in the background. Phynxa fills them in; adjust the description if you want to tell the model more.
  5. Choose Add tool, then Save the agent.

If no app appears, the dialog says "No connected app can be a tool yet" and links to Integrations.

On calls and on WhatsApp

The same tools work on a voice agent's calls and on a WhatsApp agent's chats. For a WhatsApp agent, open its Tools tab and follow the same steps (see Create a WhatsApp agent). The agent uses the app with the account you connected, in the chat just as on a call. Two things differ:

  • It always waits for the answer. On WhatsApp the agent has the app's answer before it writes back, so the Run in the background choice only matters on calls.
  • Anyone who writes to the number can set it off. A WhatsApp agent answers every customer, so give it only actions you are happy for any customer to cause. Reading a mailbox, for example, belongs on a private agent, not on your public number.

What each action does

AppActions an agent can use
HubSpot, Salesforce, Zoho CRM, GoHighLevelCreate lead, Add note, Fetch customer history, Update contact, Create task; Create ticket (HubSpot, Salesforce, Zoho CRM)
PipedriveAdd note, Fetch customer history, Update contact, Create task
CalendlyFind available times, Book meeting, Create scheduling link, List scheduled events, Cancel event, List event types
Google CalendarCreate calendar event, List calendar events, Cancel event
Google MeetCreate meeting link, Schedule meeting
Google SheetsAdd row, Find rows, Update row
GmailSend email, Search emails, Read email, Read conversation, Reply to email, Create draft, Mark as read, Archive email, Move to trash
SlackSend message, Send direct message
OutlookSend email, Search emails, Read email, Read conversation, Reply to email, Create draft, Mark as read, Archive email, Move to trash, Create calendar event, List calendar events, Cancel event
OneDriveUpload file, Search files, List folder
ShopifyFind order, Find customer, Create customer, Find product
AirtableFind records, Get record, Create record, Update record
NotionCreate page, Append to page, Search, Add comment
AsanaCreate task, Update task, Add comment, Get task, List tasks
Jira Service ManagementCreate ticket, Add comment, Get ticket
n8nTrigger workflow

Not every action of an app is offered. Actions that need an id the agent cannot look up (changing a deal's stage, for example) and actions that only set an app up (listing workflows or request types) are left out.

Configuration details

  • Background by default for writes. Actions that change something (create, send, book, cancel) default to Run in the background, so the agent keeps talking. Lookups (find times, fetch history) wait, because the reply depends on the answer.
  • Times. Actions that take a time use ISO format with a time zone (the agent knows its own time zone and the current time, so "tomorrow at 3" works).
  • Whose account. The action runs with the account you connected.
  • A connected-app tool has no endpoint, parameters or authentication to edit: those are fixed by the action.

Testing

Use the agent's Chat test and ask for the action ("Book me tomorrow at 3"). Then check the app itself for the result.

Expected result

The app shows the new record, event or message, and the Integrations page logs the request.

Troubleshooting

  • The tool says the app is not connected. Reconnect it under Integrations.
  • "The connected app could not be reached." A temporary problem on the app's side; try again.
  • See each app's page for its own errors.

Something here does not match what you see in the dashboard? Let us know.