What a connector is
A connector is the unit of integration. Each connector exposes an application’s API as a set of triggers (events that can start workflows) and actions (things that can happen inside workflows). A Salesforce connector handles OAuth to Salesforce, translates between Salesforce’s API shape and Tray.ai’s workflow model, and surfaces the specific triggers and actions that make sense — new lead, opportunity closed, case updated, contact created.
Without a connector, you’d build each integration from raw HTTP. Connectors reduce that to configuration: pick the action, point at the data, ship.
The anatomy of a good connector
- Authentication handled centrally — OAuth, API key, JWT, whatever each vendor requires.
- Trigger events surfaced as first-class workflow starters.
- Actions typed correctly and surfaced in the visual builder.
- Rate limiting and retries baked in so your workflow doesn’t hammer the vendor’s API.
- Error surfaces visible — you see what broke, not just that something did.
- Versioning — connectors update over time; you can stay on a stable version.
Tray.ai’s library
700+ pre-built connectors spanning CRM, ERP, HRIS, data warehouses, messaging platforms, dev tools, finance systems, marketing stacks, AI services, and more. Plus a universal HTTP client for anything with an API, and a Connector Development Kit for building your own.
Every connector is usable as:
- A step in an Intelligent iPaaS workflow.
- A tool for a Merlin Agent Builder agent.
- An MCP tool through Agent Gateway.
That’s what “shared library” means — build once, available everywhere.
Pair integrations
Beyond individual connectors, specific pairings — like 15Five + BambooHR or Salesforce + NetSuite — have their own pages that describe the typical workflows teams build between those two apps.