Automations can use connected accounts to cryptographically sign (or otherwise authenticate) arbitrary HTTP requests for a specific service provider.

This opens up entire third-party APIs to bots, rather than only offering a few hand-picked actions.

The owner of a connected account determines how it’s shared. For instance, a corporate ActivityPub account could be shared by an entire team, while a worker’s private Salesforce account could be accessed by only them and their bots.

We have integration examples for many popular services:

• Amazon Web Services
• Dropbox
• Facebook
• GitHub
• LinkedIn
• Salesforce
• Slack
• Stripe
• Twilio

We recommend creating an automation function for each service (e.g. Facebook Bot) to act as a delegate. That way the credentials and API interaction for a particular service are handled in a single place, and any number of other automations can use automation.function: to interface with those services in a secure and reusable way.