What connects, and what does not yet
No connector ships in the product today. What is live is an authenticated inbound endpoint: anything that can make an HTTPS request with your workspace secret reaches the system through it, starts a run and appears in the execution record. Everything below is either work our Studio has delivered for clients as a project, or roadmap — and each entry says which.
The directory
14 entries. 3 work today as part of the product, 10 our Studio has delivered before as scoped projects.
14 of 14
Salesforce
Studio has built this before and will build it again as a scoped project.
Authenticates with: OAuth 2.0, connected app
Zoho
Studio has built this before and will build it again as a scoped project.
Authenticates with: OAuth 2.0
Google Calendar
Studio has built this before and will build it again as a scoped project.
Authenticates with: OAuth 2.0, per Google account
Stripe
Studio has built this before and will build it again as a scoped project.
Authenticates with: Restricted API key, or Stripe Connect
DATEV
Studio has built this before and will build it again as a scoped project.
Authenticates with: DATEV-issued credentials
Xero
Studio has built this before and will build it again as a scoped project.
Authenticates with: OAuth 2.0
QuickBooks
Studio has built this before and will build it again as a scoped project.
Authenticates with: OAuth 2.0
Shopify
Studio has built this before and will build it again as a scoped project.
Authenticates with: Admin API access token, per shop
Custom API connection
Ships in the product and works end to end. Nothing carries this yet.
Webhooks (inbound)
Ships in the product and works end to end. Nothing carries this yet.
Webhooks (outbound)
Ships in the product and works end to end. Nothing carries this yet.
Zapier
Studio has built this before and will build it again as a scoped project.
Authenticates with: API key on our side
Postgres
Studio has built this before and will build it again as a scoped project.
Legacy / on-premise systems
Scoped case by case against the system in question.
What Systeni does not connect to
Named here rather than shown as cards you cannot press. Each of these needs something we cannot obtain by writing code — a Meta business review, a carrier account, an OAuth client, a partner contract.
- WhatsApp Business
- Facebook Messenger
- SMS
- Email (IMAP/SMTP)
- Telephony (SIP)
- Slack
- Microsoft Teams
- HubSpot
- Pipedrive
- Microsoft 365
- Calendly
- Lexoffice
- WooCommerce
- REST API
- Webhooks (outbound)
- Make
Most of them can be reached today anyway, without waiting for any of that: a custom connection calls their API with your own key. If the system you need has an HTTP API — and almost all of these do — you can connect it from the console this afternoon.
The exceptions are the ones where the restriction is the vendor's rather than technical: WhatsApp, Instagram and Messenger require a Meta business review, and telephony requires a carrier account and a number.
How a custom connection worksWhat the states mean
Four words, each meaning exactly one thing. They are the contract this page has with you.
Ships in the product and works end to end. Nothing carries this yet.
3 of 14
Studio has built this before and will build it again as a scoped project.
10 of 14
Scoped case by case against the system in question.
1 of 14
The endpoint is live today
While the connectors are built, anything that can make an HTTPS request can already hand work to Systeni — and every run it starts is inspectable, governed by your policies, and stops for a person where you say it should.