Dragwyb Docs Dragwyb Docs
Visit Website
Updated on Oct 18, 2026

Connections and Business Integrations

Manage credentials and connect supported external services to workflow actions.

AI Agent Workflows includes built-in actions for Google Sheets, WhatsApp Cloud API, Telegram Bot API, Slack Incoming Webhooks, outbound HTTP requests, and WordPress operations. Some actions use a saved connection; others take their credential or webhook URL directly in the node settings.

Choose the right integration setup

  • Saved connections: Use the Connections manager for Google OAuth, Telegram bot tokens, WhatsApp access tokens, and optional authentication on HTTP requests. See Create a Workflow Connection and Manage Workflow Connections.
  • Google Sheets: Authorize a Google account, then select a Google Sheets action and configure its spreadsheet ID, sheet tab, and any action-specific fields. See Send Workflow Data to Google Sheets.
  • Messaging: WhatsApp and Telegram use saved access-token connections. Slack uses an Incoming Webhook URL and message text directly in its action; it does not use the Connections manager in this implementation. See the WhatsApp, Telegram, and Slack guides.
  • HTTP requests: Configure a URL, method, optional headers, and optional request body. A saved connection can add supported Authorization headers. See Send HTTP Requests from a Workflow.
  • WordPress actions: Use built-in nodes to query or change posts, users, roles, comments, media, taxonomies, terms, and plugin activation state. WordPress permissions and the specific action’s validation still apply. See Run Native WordPress Actions.

    • Screenshot to add: Agent Workflows Connections page and workflow action picker

    Before you build an integration workflow

  • Confirm that the external service, API, bot, or Google Cloud project is available and configured.
  • Use a test workflow and non-sensitive sample data before connecting a production process.
  • Map only the fields the destination needs. Avoid sending credentials or private customer data in messages, request bodies, or logs.
  • Check the node result and run log after a test. A successful HTTP response is not the same as proof that a human received or acted on a notification.