Integrations
One Mission. Across your stack.
A Mission works across the systems the job depends on — and asks for only the access that job needs. You don't pick integrations first. You describe the outcome, and Ziggyy tells you which systems it needs and why.
- Only the systems a Mission needs.
- Only the access it needs.
- You approve what matters.
Start from the Mission
The Mission decides the systems — and the access.
One Mission, as Ziggyy defines it: each system it needs, why, what it may do there, and what it will never touch.
Product preview · connections are simulated
Example Mission · “Put Amazon orders over $500 into our Google Sheet.”
Amazon Seller CentralRequired
Source of truth for orders
Needs access to
- Read new orders
- Read order details
Doesn't need access to
- Refund orders
- Cancel orders
- Change orders
Limited to: Orders only
Google SheetsRequired
Destination for qualifying orders
Needs access to
- Check which orders are already there
- Add new matching orders
- Update a row when its order changes
Doesn't need access to
- Delete rows or spreadsheets
Limited to: Only the Orders spreadsheet — no other files
SlackOptional · suggested
Tells Operations when an order can't be synced
Needs access to
- Post exception alerts
Limited to: Only #operations
- Required
- The Mission can't finish without it. Amazon Seller Central is the source of truth for orders.
- Optional
- It makes the Mission better, and never blocks it. Slack tells Operations when an order can't sync.
- Alternative
- One of several can do the job. Invoices arrive in Gmail or Google Drive — you choose which.
Contextual connections
Connection isn't permission.
Most tools ask for access to everything up front. Ziggyy separates four things, so connecting a system never means handing over unrestricted autonomy.
Organization connection
Your company connects a system once. That alone lets Ziggyy do nothing.
Mission access
Each Mission is granted only the capabilities it needs, on only the resources it needs.
Action controls
Each action is automatic, asks first, or is never allowed.
Approval policy
Who approves what — amounts, recipients, sensitive changes.
Least privilege
Access with a reason. And a clear “no”.
Example Mission · “Reconcile supplier invoices against purchase orders every week.”
GmailRequired
Where supplier invoices arrive
Needs access to
- Find supplier-invoice messages
- Read those messages and their attachments
Doesn't need access to
- Send email
- Delete email
The “doesn't need” list is a feature, not small print.
The catalog
Can Ziggyy work with your systems?
Search by name or by the kind of system. Each status comes straight from the product's own catalog, and nothing is marked available until it is.
25 in preview · 11 planned — plus custom systems and APIs. Production connectors are in development; nothing here is marked available until it is.
- Available
- Production connection, ready for live Missions.
- Preview
- Works end to end in the Mission setup preview with a simulated connection. The production connector is in development.
- Planned
- On the roadmap. Meanwhile a Mission can include it through a custom connection request.
- Custom / API
- An internal system, database or API, connected with your team where supported.
- GmailGoogle Workspace emailPreview
- OutlookMicrosoft 365 emailPreview
Files & knowledge
- Google DriveGoogle Workspace files and shared drivesPreview
- SharePointMicrosoft 365 files and document librariesPreview
- DropboxFile storage and sharingPreview
- BoxEnterprise content and file storagePlanned
Collaboration
- SlackTeam messaging and channelsPreview
- Microsoft TeamsMicrosoft team chat and channelsPreview
CRM & sales
- HubSpotCRM for contacts, companies and dealsPreview
- SalesforceCRM for leads, accounts and opportunitiesPreview
- PipedriveSales pipeline CRMPlanned
Ecommerce
- Amazon Seller CentralAmazon marketplace orders and listingsPreview
- ShopifyOnline store orders, products and customersPreview
Finance & accounting
- NetSuiteERP for purchasing, accounting and inventoryPreview
- QuickBooksSmall-business accounting and invoicingPreview
- XeroCloud accounting and invoicingPreview
- SAPEnterprise ERPPlanned
- SageAccounting and business managementPlanned
- StripePayments, invoices and subscriptionsPreview
Customer support
- ZendeskCustomer support tickets and help deskPreview
- IntercomCustomer messaging and support inboxPreview
Analytics & monitoring
- GA4Google Analytics 4 website and app analyticsPreview
- MixpanelProduct analyticsPlanned
- UptimeRobotWebsite and service uptime monitoringPlanned
- DatadogInfrastructure and application monitoringPlanned
Spreadsheets & workspaces
- Google SheetsGoogle Workspace spreadsheetsPreview
- ExcelMicrosoft 365 spreadsheetsPreview
- AirtableSpreadsheet-database hybrid for teamsPreview
- NotionDocs, wikis and team knowledgePlanned
- TypeformOnline forms and surveysPlanned
Projects, code & data
- JiraIssue and project trackingPreview
- LinearIssue tracking for product teamsPreview
- AsanaWork and project managementPlanned
- MondayWork management boardsPlanned
- GitHubCode, pull requests and issuesPreview
- PostgreSQLRelational databasePreview
Custom systems & APIs
Beyond the household names
Your business runs on more than the logos.
An internal ERP. A regional accounting system. A database. A specialist tool with an API. A Mission describes what it needs in capabilities — read orders, update a record — not in vendor names, so those needs can be met by a custom connection where one can be supported.
- Internal ERP
- Custom API
- PostgreSQL database
- Specialist line-of-business system
Custom connections are set up with your team. They're never instant, and Ziggyy says so.
Start from the Mission. Ziggyy works out the systems.
Describe the outcome, and Ziggyy tells you which systems it needs, why, and what it will never touch.