Relayfile mounts a provider as files. Every integration below becomes a directory an agent can read, write, and watch: /slack/channels/..., /linear/issues/..., /github/pulls/.... Same shape for all of them, so an agent that works against one works against the rest.
Issues and projects
- Linear
- Jira
- Asana
- ClickUp
- Notion
- Confluence
- Airtable
Code and CI
- GitHub
- GitLab
- DDocker Hub
- DDaytona
Messaging
- Slack
- Microsoft Teams
- Telegram
- Intercom
Email and calendar
- Gmail
- Google Calendar
- Calendly
- SendGrid
- Mailgun
Files and storage
- Google Drive
- Dropbox
- Box
- OneDrive
- SharePoint
- AAmazon S3
- GGoogle Cloud Storage
- Azure Blob Storage
CRM and support
- Salesforce
- HubSpot
- Pipedrive
- Zendesk
Commerce and payments
- Stripe
- Shopify
Analytics
- Segment
- Mixpanel
Data and infrastructure
- PPostgres
- RRedis
- NNeon
- GGoogle Cloud
- Cloudflare
Meetings
- Granola
- Fathom
- Recall
Social
- X
Adding one is cheap
We don't hand-build every connection. Relayfile sits on top of Nango and Composio, which between them already broker auth and sync for thousands of APIs. An adapter's job is the small part: map a provider's resources onto a file tree, declare its triggers, and describe how writes flow back.
That means the list above is what we've shipped, not what's possible. If your provider is in Nango's or Composio's catalog, wiring it up is an adapter, not an integration project.