What is a Prebuilt Connector?

Rather than every team reimplementing OAuth handshakes, pagination, rate-limit handling, and field mapping for, say, Salesforce or Slack, a prebuilt connector packages all of that once and exposes a simpler set of actions and triggers ("send a message," "create a record," "new email received") that a workflow can call directly. This is the core value proposition of integration platforms and automation tools — the connector library is often the actual product, more than the workflow engine sitting on top of it. Connector quality varies a lot in practice: a good one handles token refresh transparently, respects the provider's rate limits with backoff, and surfaces provider-specific errors in a normalized way; a thin one just wraps the raw API and pushes all of that complexity back onto the integration builder. Connectors also need maintenance as providers change their APIs, deprecate fields, or update auth requirements — an unmaintained connector silently breaks integrations built on top of it. When no prebuilt connector exists for a needed service, the alternative is a custom point-to-point integration built directly against that provider's raw API, with all the auth and mapping work the connector would otherwise have handled.