> ## Documentation Index > Fetch the complete documentation index at: https://docs.collabase.ch/llms.txt > Use this file to discover all available pages before exploring further. # Connectors > Connect Collabase automations to third-party services — from Slack to Stripe to GitHub. # Connectors Connectors are pre-built integrations that let your automations read from and write to external services. Each connector defines its own **triggers** (events that start an automation) and **actions** (operations the automation performs). No custom code is required. ## How connectors work Every automation step that calls an external service uses a connector. When you add an action node to the builder, you select the connector, configure the action, and map input fields from previous steps using `{{variable}}` syntax. Credentials are stored securely per-connector. Each connector has a **Test Connection** button that verifies credentials before you save them. ## Available connectors Post messages, send DMs, manage channels and reactions Send channel messages, create meetings, manage teams Send messages, embeds, manage threads and roles Send messages and media via WhatsApp Business API Send messages and media via Telegram Bot API Transactional email with templates and tracking SMS, MMS, WhatsApp, and voice calls via Twilio SMTP email using your server's mail configuration Create events, check availability, manage calendars Microsoft 365 calendar events and scheduling assistant Retrieve events, invitees, and create scheduling links Upload, move, share, and manage Drive files Read, append, update, and search spreadsheet rows Upload from URL, list folders, move, and share files Full CRUD on Airtable records with filtering and views Create and update pages, query databases, search Contacts, deals, companies, tickets, and pipeline events Deals, persons, organizations, activities, and notes Payments, customers, subscriptions, invoices, refunds Issues, pull request comments, and workflow dispatch Issues, merge requests, pipelines, and file creation Create, update, and transition Jira issues Issue lifecycle, comments, and team management Task CRUD, comments, and project listing Cards, lists, labels, comments, and board management Items, board columns, updates, and group management Issue triage, releases, and project monitoring Events, metric queries, monitors, and incidents Incident lifecycle, escalation, and on-call management Chat, images, embeddings, moderation, Whisper, TTS Swiss ERP: contacts, invoices, and projects Swiss ERP: customers, orders, and financials Employee records, absences, and HR sync Call any external API with full request control Ollama-compatible LLM prompts and summaries Format dates, filter arrays, and reshape data Run custom JavaScript inside an automation step ## Authentication Each connector uses one of four authentication types: | Type | How to configure | | ------------- | ---------------------------------------------------------------------- | | **API Key** | Enter the key directly in the connector credential form | | **OAuth 2.0** | Generate a token from the service's developer console and paste it in | | **Basic** | Username and password | | **None** | No credentials required (e.g. Email, Transform, HTTP with public APIs) | Credentials are encrypted at rest. They are never logged or exposed in automation output variables. Connector credentials are workspace-scoped. Any member with **Automation: Edit** permission can select existing credentials when building an automation, but cannot view the raw credential values.