Skip to main content

Use Connections Safely

Connections let Siesta AI work with external tools. In the Connections section, you can see integrations such as Gmail, Google Calendar, Google Drive, Slack, Jira, HubSpot, Google Search, OpenAI, SharePoint, Azure Storage, and REST API connections.

Personal Connections​

Personal connections usually use your permissions in the external service. If you connect email, calendar, or files, Siesta AI can only access what that account allows.

Reconnect a personal connection if authorization expires, your password changes, or the external service asks for new consent.

Shared Connections​

Shared connections are managed by an administrator. They may use a service account or shared API credentials. If a shared connection is missing or fails, contact your admin rather than creating a duplicate.

What to Check Before Using a Tool​

  • Whether the connection is personal or shared.
  • Whether the action only reads data or changes another system.
  • Whether the agent should show a preview before a write action.
  • Whether approval is required before the action runs.
  • Whether the target system should be checked after the action.

You do not need to review OAuth scopes, token limits, approval policy details, MCP configuration, or API payloads for normal use. Ask an admin when a shared connection is missing, a write action is blocked, a permission error appears, or a tool needs broader access than you expected.

Safe Usage​

Before asking an agent to send, update, delete, or publish anything, confirm which connection it will use and ask for a preview when the action matters.

Examples of actions that should usually be previewed first: sending Gmail, creating calendar events, posting Slack messages, creating Jira tickets, editing HubSpot records, or updating files.

Function-Level Approvals​

Connections are made of individual functions. One function might only read data, such as searching Drive files or listing calendar events. Another function in the same connection might write data, such as sending an email, creating a ticket, updating a CRM record, deleting a file, or publishing content.

Admins can configure approval per function. Safe read-only functions are often allowed to run directly. Riskier write, send, delete, publish, or external-trigger functions should ask for approval before Siesta AI completes the action.

As a user, you do not need to manage those settings. You should still ask for a preview when the result matters, and expect some actions to pause with Waiting for approval before they run.

Connection Recipes​

Authorize Your Personal Tool​

  1. Open Connections.
  2. Search for the tool, such as Gmail, Google Calendar, Google Drive, or Outlook.
  3. Start the authorization flow.
  4. Approve the requested permissions in the provider screen.
  5. Name the connection so you can recognize it later.
  6. Return to the agent or workflow and try a small read-only request first.

Ask Safely Before a Write Action​

Use my Google Calendar connection to prepare a 30-minute meeting invite.
Show me title, attendees, description, and time first.
Do not create the event until I approve.

Report a Broken Shared Connection​

Send your admin the connection name, agent or workflow name, action you tried, error message, and whether the action appears in Tool Executions.