Skip to main content
Integrations are managed connections to external services. They are the configuration layer that powers integration-backed tools and connected workflows.

​
Integrations vs Tools

  • Integrations store the connection to a service
  • Tools are the actions an agent performs using that connection
For example, an integration might connect Feather to a scheduling platform, while the tool created from that integration checks availability or books time.

​
Typical Uses

  • CRM lookups and updates
  • Scheduling and appointment systems
  • Domain-specific systems of record
  • Secure access to third-party APIs across multiple agents

​
List Available Integrations

curl "https://prod.featherhq.com/api/v1/integrations" \
  -H "X-API-Key: $FEATHER_API_KEY"

​
Integration Instances

An integration instance is your organization’s configured connection for one service. You can have multiple instances when teams, environments, or business units need different credentials or behavior. Common pattern:
  1. Inspect the available integrations
  2. Create an instance with the right credentials or settings
  3. Enable or reference the resulting capability through tools or agent configuration

​
Design Guidance

  • Use integrations when the same external system should support multiple agents.
  • Use a custom tool when the action is unique to your own backend and does not need a reusable connection model.
  • Keep external side effects in integrations or tools, not inside prompts.

​
Adjacent Features

Some connected capabilities live in dedicated APIs rather than the generic integrations API, including:

Available Integrations API

See the catalog of supported integration types.

Integration Instances API

Create and manage organization-specific integration instances.

Tools

Expose connected capabilities to agents through tools.

Calendars

Use calendar-specific connections and booking flows.