Integrations
Your systems play their part.
metamorphOS runs the process on the stack you already have. Your systems start it, feed it, and carry out its actions. Nothing gets replaced.
It works in both directions.
The process calls your systems.
A step can call any REST endpoint: create the record, file the document, post the entry. The response flows straight back into the run.
How metamorphOS signs in to your systems:
The process waits for your systems.
A run can wait on a webhook, matched on your own data: the payment reference, the order number. When it arrives, the payload enters the process as if someone had typed it in, and the run moves on. A webhook can also start a run of its own.
How we make sure it is really your system calling:
Not every partner has an API. Everyone has email.
The subcontractor, the customer, the authority: they will never call your endpoints. They answer emails. So the process speaks email, natively.
A process gets its own address. What lands there is read: sender, subject, text, and every attachment, filed with the run.
The timesheet, the signed offer, the one-line "approved": it reaches the right run, and the run moves on. A mail can start one, too.
Forward a thread to the process and it reads the original: real sender, real content, attachments included. Not the forward.
Every inbox has its allowlist: only senders you approve get through.
Bring your own API. In minutes.
Our own integration engine turns any REST API into process steps. With an OpenAPI spec, it takes seconds.
Endpoints, parameters and auth are read from your OpenAPI file automatically.
OAuth 2.0 and API keys for calls out, signed webhooks for calls in.
Every delivery logged and inspectable, every connector versioned.
The tools teams run this on.
A selection, not a ceiling: anything with a REST API docks on in minutes.
Microsoft Teams
Salesforce
Notion
HubSpot
Google Drive
Email (SMTP/IMAP)
Asana
Trello
Monday.com
Miro
Confluence
Wrike
Microsoft Outlook
Google Mail
Google Calendar
Calendly
Microsoft SharePoint
Microsoft OneDrive
GitHub
GitLab
Zenhub
DocuSign
Dropbox
Google Sheets
Pipedrive
Zendesk
Freshdesk
ServiceNow
Shopify
Stripe
Workday
Personio
Factorial
FreshBooks
NetSuite
Odoo
Airtable
DATEV
sevDesk
Requesty
Slack
Wix
Grafana
Anthropic Claude
Google Gemini
Jira
Freshsales
MoodjaSomething proprietary? We build the connector with you. Legacy systems, industry software, in-house tools: our engineering team builds the connector alongside your first process.
integrations@metamorphos.ioConnecting up, answered.
Nineteen connectors are built today, with around 246 named operations between them: Odoo, HubSpot, Freshsales, Jira, GitHub, GitLab, Trello, Slack, Google Calendar, Google Drive, Google Mail, Microsoft Outlook, Shopify, Wix, sevDesk, Grafana, Anthropic Claude and Google Gemini. Everything else with a REST API connects through OpenAPI import.
Anything with a REST API docks on. Our integration engine turns endpoints into process steps, and with an OpenAPI spec the endpoints, parameters and auth are imported automatically.
Yes. A step can call your systems and use the response in the run, and a run can wait on a webhook matched on your own data, such as a payment reference or an order number. A webhook can also start a run.
Outbound: OAuth 2.0 with Auth Code and PKCE or Client Credentials, API keys, or Basic. Inbound: HMAC with SHA-256 or SHA-512, JWT and JWS with RS and ES, JWKS key rotation and replay protection.
They take part in the process itself, through a secure task link verified by email. Email remains the fallback: a process has its own mailbox, senders are allowlisted, and what arrives is filed with the run, attachments included.
Yes. For legacy systems, industry software and in-house tools, our engineering team builds the connector alongside your first process.
Show us how you work today.
You'll know what to fix first.
A discovery call with Robert: thirty minutes on where coordination costs you most.