Connector

A connector (sometimes called an "app," "integration," or "connection" depending on the platform) is the pre-built software layer that translates between a no-code automation platform's generic trigger/action framework and a specific third-party application's actual API — so a builder can configure "Create Row in Airtable" or "Send Message in Slack" through a simple visual form, without knowing that under the hood, this triggers an authenticated POST request to `https://api.airtable.com/v0/{base_id}/{table_name}` with a specific JSON schema. Why it matters: the size and quality of a no-code platform's connector library is often the single biggest driver of adoption — Zapier's 7,000+ connectors versus a smaller competitor's 500 is a meaningful practical difference for a builder whose stack includes a niche tool. Connector quality also varies significantly: a well-built connector exposes most of the underlying API's capability (multiple trigger types, rich field mapping, proper pagination and error handling), while a thin or poorly maintained connector might only expose a handful of basic operations, forcing builders to fall back on generic HTTP/webhook modules to access functionality the connector doesn't cover. How it works: connectors are typically built by either the automation platform's own team, the third-party app's own team (a "premium" or "verified" connector, generally higher quality since the app vendor maintains it), or the community (open-source connector frameworks like n8n's node system allow anyone to contribute a new integration). Building a connector involves defining the available triggers (which webhook events or polling endpoints are exposed), the available actions (which API operations are exposed, and what input fields/validation they require), and the authentication method (API key, OAuth 2.0, Basic Auth) the connector handles on the builder's behalf. Worked example — from the builder's perspective, using the Slack connector in Zapier: you click "Connect Slack," get redirected through Slack's OAuth consent screen ("Zapier wants to: post messages, read channel list"), authorize it, and are returned to Zapier — no API key copying, no reading Slack's API docs. You then pick the action "Send Channel Message," and the connector auto-populates a dropdown of your actual Slack channels (fetched live via the API) rather than requiring you to type a channel ID. This abstraction — turning "make an authenticated HTTP POST to a specific endpoint with a specific payload shape" into "pick a channel from a dropdown, type a message" — is the entire value proposition of a connector, and by extension, of no-code platforms generally.