[Webinar] Improving Service Quality & Compliance in Homecare Via AI: What Works And What Doesn’t

Integrations

Your workflows run in Google Workspace.
But they don't have to stay there

Zenphi is a workflow automation platform built natively for Google Workspace. Operational processes rarely stay inside Google — approvals update QuickBooks, onboarding workflows provision accounts across five systems, invoices trigger DocuSign requests and Slack notifications.
Zenphi connects to the systems your processes actually touch — as named steps in a governed workflow, with full audit trail.

100+ native integrations · Any system via HTTP/API · Flat pricing — no per-run, no per-connection fees

How a workflow connects your systems
Trigger
New hire in HRIS BambooHR · Workday · webhook
Step
Create Google Workspace account Admin Console · assign OU · set groups
AI Step
Generate welcome pack Gemini · role-based content
Step
Send for e-signature DocuSign · offer letter + NDA
Human
IT manager confirms provisioning One-click from Gmail
Step
Update HRIS record Status set to Active · accounts logged
Step
Notify manager in Slack New hire ready · first day details
How Zenphi connects to your tools

Not a connector platform. A workflow platform that connects.

There's an important distinction between what Zenphi does and what tools like Zapier or Make do. Zapier connects two tools and passes data between them — useful for simple triggers and lightweight syncs. Zenphi builds the full workflow — with conditions, approvals, human-in-the-loop steps, AI model steps, error handling, and audit trail — and external systems are included wherever they're part of the process.

When a vendor invoice is processed in Zenphi, QuickBooks doesn't receive data because Zenphi and QuickBooks are "connected." QuickBooks receives data because the approval was granted, the extracted values were validated, and a configured workflow step says: update this record with these specific fields. You control exactly what data moves, when it moves, and what has to happen before it moves.
01
Trigger from external systems
Your CRM closes a deal. Your HRIS records a termination. Zenphi can listen to events in external systems and starts the right workflow automatically.
02
Include external systems as workflow steps
Create a record in Salesforce. Update a QuickBooks invoice. Update a status in a case management system. These are named, configured steps inside a Zenphi workflow.
03
Connect anything with HTTP and API
Zenphi has first-class actions for 100+ popular tools like Salesforce, HubSpot, Xero, Jira, Asana and more. For others, the HTTP step lets you pass workflow data as parameters, receive the response, and use it in subsequent steps.
Better than native integrations

For most tools, Zenphi gives you more control than the native integration does

Native integrations between tools are designed for the common case. They sync what the integration designer thought you'd need. If your process requires a conditional sync, a different field, or an action that only happens after a human approval — the native integration usually can't do it. In Zenphi, every connection to an external system is a configured workflow step. You choose exactly which fields to send, under what conditions, in what sequence, and after what has happened earlier in the workflow. The integration doesn't drive the workflow. The workflow drives the integration.
Conditional data sync
Don't send data to a system blindly. Send it only when conditions are met — invoice approved, compliance check passed, field values validated. Native integrations sync on event. Zenphi syncs on outcome.
Field-level control
Map exactly which workflow data goes to which system field. Not everything the source system knows — just what this process needs to record, in the format the destination system expects.
Sequenced actions across multiple systems
One workflow can update QuickBooks, send a DocuSign request, post a Google Chat notification, and create a Jira ticket — in sequence, with the right data at each step. No separate automations that might fire in the wrong order.
Audit trail across every system touched
Every external system action in a Zenphi workflow is logged: what data was sent, when, by which workflow step, after which approval. Not just what happened inside Zenphi — what the workflow caused to happen everywhere else.
100+ native integrations

First-class actions
for the tools your teams already use

Workflow steps that already exist within Zenphi and can be used to create, update, read, delete, trigger next actions or added as a logic development of the existing process.
Finance & Accounting
Document & E-Signature
Project Management & Ticketing
Communication
AI Agents
Gemini
OpenAI
Claude
Data & Databases
Airtable
MySQL
MongoDB
Identity & Directory
Microsoft Azure AD (Entra ID)
Okta
MongoDB
ERP & Operations
SAP
Oracle
Odoo (via API)
Any system with an API — HTTP / REST
If a system has an API, Zenphi can connect to it. The HTTP step gives you full control — method, headers, body, authentication, and response mapping to workflow objects.

Don't see your tool? With Zenphi, you're still 20 minutes away from uing it within your workflow

Our product team ships first-class actions faster than we manage to add them to the website. Tell us what tool you're using in your business process, and we'll let you know if we already have first-class actions for it, if they're on the product roadmap, or show you how to set up a connection via the HTTP action in 20 minutes or less.
triggers

Start a Zenphi workflow from a Google Workspace event — or any in any external system

Zenphi has a widest range of native Google Workspace-related triggers. However, your automation doesn't have to start from a Google Workspace event. Any external system that can send a webhook or make an HTTP call can trigger a Zenphi workflow automatically.
HTTP Triggers
External system fires — workflow starts
Any external system that supports API connections can trigger a Zenphi workflow. The payload data is available as objects in the workflow from step one.
Scheduled triggers
Time-based — no event needed
Run workflows on a schedule — hourly, daily, weekly, or a custom cron expression. Useful for batch document processing, recurring compliance checks, scheduled report generation, and any process that runs on cadence rather than an event.
Google Workspace events
Native Google triggers
Gmail email arrived, Drive file uploaded, Form submitted, Calendar event created, Admin Console user created or suspended — native Google Workspace events can work as a trigger, with full access to the event data in every subsequent step.
Zenphi is not Zapier

A tool that connects apps. A platform that automates processes. These are different things

Zapier is genuinely useful. When something happens in one app and you want something to happen in another — no conditions, no approvals, no audit trail — Zapier is often the right tool.

Zenphi is for a different job. When a process crosses multiple systems, involves human decisions, requires AI to read or generate content, needs governance and audit trail, and has to run reliably at scale — that's a Zenphi workflow. The external systems are part of the process, not the point of it.

The practical difference: in Zapier, the integration is the automation. In Zenphi, the workflow is the automation, and the integrations are steps inside it.
Capability Zapier / Make Zenphi
Core purpose Connect apps, pass data Automate end-to-end business processes
Workflow structure Trigger → action (linear) Multi-step with conditions, loops, subflows
Approval chains Not supported Sequential, parallel, conditional
Human-in-the-loop Not supported At any configured step
AI model steps Limited Gemini, GPT-4o, Claude — any model
Google Admin Console Not available Full Admin API — native
Audit trail Not built in Every step logged — built in
Pricing model Per task / per run Flat — no per-run, no per-connection fees
Best for Lightweight data sync between SaaS tools Operational workflows that cross systems, teams, and AI
Core purpose
Zapier / Make Connect apps, pass data
Zenphi Automate end-to-end business processes
Workflow structure
Zapier / Make Trigger → action (linear)
Zenphi Multi-step with conditions, loops, subflows
Approval chains
Zapier / Make Not supported
Zenphi Sequential, parallel, conditional
Human-in-the-loop
Zapier / Make Not supported
Zenphi At any configured step
AI model steps
Zapier / Make Limited
Zenphi Gemini, GPT-4o, Claude — any model
Google Admin Console
Zapier / Make Not available
Zenphi Full Admin API — native
Audit trail
Zapier / Make Not built in
Zenphi Every step logged — built in
Pricing model
Zapier / Make Per task / per run
Zenphi Flat — no per-run, no per-connection fees
Best for
Zapier / Make Lightweight data sync between SaaS tools
Zenphi Operational workflows that cross systems, teams, and AI
Integrations

Connecting Your Tools to Google Workspace
— Frequently Asked Questions

Answers to the questions teams ask when native integrations fall short and operational workflows need to span multiple systems.

Native point-to-point integrations between Salesforce and QuickBooks are notoriously fragile — they sync what the integration designer thought you'd need, and break the moment your process requires a condition, a field that doesn't map cleanly, or an action that only happens after something else has occurred first.

Zenphi solves this by replacing the native integration with a governed workflow step. Instead of Salesforce and QuickBooks talking directly to each other on event, Zenphi orchestrates the full sequence: a deal closes in Salesforce, Zenphi reads the relevant data, applies any validation or conditional logic your finance process requires, and writes the correct record to QuickBooks — with exactly the fields you specify, at exactly the right point in the process. Both systems receive the data. You control what, when, and under what conditions. Every action is logged. Because Zenphi has first-class native actions for both Salesforce and QuickBooks, there is no custom connector to build or maintain. The workflow can include approval gates, conditional branching, and notifications alongside the data sync — capabilities no native integration supports. Flat pricing — no per-sync fees.

Connecting Asana to Google Workspace through a native integration gives you a limited, fixed sync — typically task creation from a Google Form or a Drive file trigger, with no approval logic, no conditional routing, and no audit trail. For teams that need Asana to participate in real operational workflows, a workflow orchestration platform is the right approach.

Zenphi is the strongest option. It has first-class native Asana actions and native Google Workspace integration as its operating foundation. A Google Form submission can trigger a Zenphi workflow that runs an approval, generates a Google Doc, creates an Asana task with specific fields populated from the form data and the approval outcome, and notifies the team via Gmail — as a single automated workflow. Conversely, an Asana task state change can trigger a Zenphi workflow that updates a Google Sheet, sends a Gmail notification, or routes a document for sign-off. Every action across both systems is logged in a complete audit trail. No per-connection or per-run fees.

Native Jira integrations with Google Workspace cover basic use cases — connecting Jira to Google Docs for issue tracking, or using Google SSO. For teams that need Jira to participate in operational workflows — where a Google Form submission creates a Jira ticket, a Jira status change triggers a Google Workspace approval chain, or a Jira ticket resolution triggers a document to be generated and filed in Drive — a workflow orchestration platform is the right approach.

Zenphi is the strongest tool for integrating Jira with Google Workspace as part of a governed workflow. It has first-class native Jira actions (create issue, update issue, transition status, add comment, query issues) alongside native integration with every Google Workspace app. IT service requests submitted via Google Forms route into Jira automatically with the correct project, issue type, and priority populated from the form data. Jira ticket resolutions trigger Google Chat notifications, Google Sheets updates, or approval workflows — all within a single Zenphi workflow where every step is logged.

Connecting Salesforce to Google Workspace natively gives you limited, fixed syncs. For teams that need Salesforce to participate in operational workflows — updating opportunity records when a Google Form is submitted, generating Google Docs proposals when a deal reaches a specific stage, or writing Salesforce contacts from Gmail intake — a workflow orchestration platform provides far more control.

Zenphi is the strongest option. It has first-class native Salesforce actions (create/update/query records across all standard and custom objects) running natively inside Google Workspace-centric workflows. A deal closes in Salesforce, Zenphi generates a Google Doc contract from a template, routes it for e-signature via DocuSign, files the signed copy in Drive, and updates the Salesforce opportunity with the execution date — as a single automated sequence. Every action in both systems is logged. Flat pricing — no per-sync fees as Salesforce record volume grows.

HubSpot's native Google Workspace connection covers surface-level use cases — Gmail tracking, calendar sync, Google Meet integration. For teams that need HubSpot to participate in real operational workflows — routing new contacts into Google Workspace sequences, generating Google Docs proposals when a deal advances, or updating HubSpot records from Google Form submissions — a workflow orchestration platform is the right approach.

Zenphi is the strongest option. It has first-class native HubSpot actions alongside native Google Workspace integration. A new HubSpot contact triggers a workflow that creates a Google Drive folder, generates a welcome document, sends a Gmail, and logs the action to a Google Sheet. A Google Form submission creates or updates HubSpot contact and deal records with exactly the fields specified. Every action across both systems is logged with a full audit trail.

Zenphi connects Pipedrive to Google Workspace as a first-class workflow step. Sales processes that begin in Google Workspace (a Form intake, a Gmail thread) can create Pipedrive contacts, add activities, and advance deal stages automatically. Pipedrive pipeline events can trigger Google Workspace actions — document generation, calendar events, Drive folder creation, Gmail notifications — all within a governed workflow with audit logging and flat pricing. No custom code or third-party connector required.

QuickBooks' native Google Workspace connection is limited to basic exports. For operational workflows — automatically creating QuickBooks invoices when a Google Form is submitted, updating bills when an approval workflow completes in Gmail — a workflow orchestration platform gives you the control that native integrations lack.

Zenphi has first-class native QuickBooks actions running inside Google Workspace-centric workflows. An invoice approval completed in Gmail triggers a QuickBooks bill update with the exact fields validated in the workflow. A new client onboarded via Google Forms creates a QuickBooks customer record. Every QuickBooks action is logged with the workflow step that triggered it, the data sent, and the timestamp. Flat pricing — QuickBooks write volume doesn't drive cost increases.

Zenphi has first-class native Xero actions running inside Google Workspace-centric workflows. Invoices arriving in Gmail are extracted by AI, validated, routed for approval through Gmail or Google Chat, and posted to Xero only when the approval is confirmed and the data passes validation — not on every event. Xero invoice status changes can trigger Google Chat notifications, Sheets updates, or document filing in Drive. Every action is logged for audit. No per-transaction fees.

Stripe doesn't have a native Google Workspace integration. Zenphi connects Stripe to Google Workspace workflows using its HTTP action layer and webhook triggers. A Stripe payment event received via webhook triggers a Zenphi workflow that logs the transaction to Google Sheets, generates a receipt document in Google Docs, sends a Gmail confirmation, and optionally updates a CRM record. Stripe subscription changes can trigger provisioning or offboarding workflows within Google Workspace — all without custom code.

PayPal has no native Google Workspace integration. Zenphi connects PayPal to Google Workspace via its HTTP trigger and action layer. A PayPal payment notification triggers a Zenphi workflow that logs the transaction to Google Sheets, generates a receipt document, and sends a Gmail confirmation to the payer — all automatically, with every action logged. For finance teams managing payment reconciliation in Google Sheets or Google Drive, Zenphi routes PayPal data into existing Google-native processes without custom development.

DocuSign has a native Google Workspace add-on for sending documents for signature from Gmail or Drive, but it handles only the signature step — not the workflow around it. For teams that need the full document lifecycle automated (generate the document, route it for internal approval, send to DocuSign, receive the signed copy back, file it in Drive, notify the team, update a tracking register), a workflow orchestration platform provides the complete sequence.

Zenphi has first-class native DocuSign actions running inside Google Workspace-centric workflows. A trigger event generates a document from a Google Docs template, sends it for signature via DocuSign, receives the completed document back, files it in the correct Drive folder with the correct permissions, and logs the full sequence for audit — all as a single automated workflow with no manual steps between generation and filing.

Zenphi connects Adobe Sign to Google Workspace as a native workflow step. Documents are generated from Google Docs templates, sent via Adobe Sign for signature at the configured point in the workflow, received back, filed in Drive, and logged — all within a single Zenphi workflow running from the triggering event to the final filing without any manual coordination. Every signature event is logged with the document reference, signee identity, and timestamp.

Zenphi connects Trello to Google Workspace in both directions. A Google Form submission creates a Trello card with fields populated from the form data. A Trello card moving to a specific list triggers a Zenphi workflow that sends a Gmail, generates a Google Doc, or updates a Google Sheet. Every Trello action within a Zenphi workflow is logged for audit, and no per-run fees apply regardless of card volume.

Zenphi connects Monday.com to Google Workspace as first-class workflow steps. A request submitted via Google Forms creates a Monday item, triggers an approval workflow in Gmail, and updates the Monday item status when the approval is completed — all in one workflow, all logged. Monday item state changes can also trigger Google Workspace actions: document generation, Drive file organization, Gmail notifications, or Sheets updates.

Zenphi has first-class native ClickUp actions running inside Google Workspace-centric workflows. A Google Form submission creates a ClickUp task with the relevant fields populated. A ClickUp task status change triggers a workflow that generates a Google Doc, sends a Gmail notification, or updates a Google Sheet. For teams where ClickUp and Google Workspace are both central operational tools, Zenphi connects events in one to governed actions in the other — with full audit trail and flat pricing.

Zenphi has first-class native Slack actions. Google Workspace workflow events (approval completions, form submissions, document generation) send structured Slack notifications with the relevant context. Slack can also be configured as a human-in-the-loop approval channel — approvers receive a Slack message and their response triggers the next workflow step. Every Slack action within a Zenphi workflow is logged with the workflow step that triggered it and the message content.

Microsoft Teams and Google Workspace are competing ecosystems with no native operational integration. Zenphi has first-class native Teams actions running inside Google Workspace-centric workflows. A Google Form submission, an approval completion, or any Google Workspace workflow event can send a structured Teams notification to the correct channel or person — keeping Teams users informed about Google Workspace workflow events without requiring them to log into Workspace for status updates.

Zenphi connects Zoom to Google Workspace via its HTTP action layer and webhook triggers. Zoom webhook events trigger Zenphi workflows that log meeting data to Google Sheets, generate Google Docs from AI-processed meeting transcripts, or send Gmail follow-up communications — all within a governed, auditable workflow sequence. No custom code required.

Outlook and Google Workspace are competing email and calendar platforms with no meaningful native operational integration. Zenphi has first-class native Outlook actions running inside Google Workspace-centric workflows. Outlook emails can trigger Zenphi workflows that process content, extract data, route for approval in Gmail or Google Chat, and update Google Workspace systems. Google Workspace workflow events can send Outlook emails or create Outlook calendar events — bridging both environments for hybrid organizations.

Zenphi bridges OneDrive and Google Drive as named workflow steps. Files uploaded to OneDrive can trigger Zenphi workflows that process the document, generate a Google Doc equivalent, or route for review in Google Workspace. Google Workspace workflow outputs can be saved to OneDrive for sharing with Microsoft-based external parties. Every file action across both platforms is logged within the Zenphi workflow audit trail.

Zenphi has first-class native SharePoint actions running inside Google Workspace-centric workflows. Documents generated in Google Workspace workflows can be filed to SharePoint for compliance or archiving. SharePoint document events can trigger Zenphi workflows that route the document through a Google Workspace approval chain, generate notifications in Gmail or Google Chat, and log the action to a Google Sheet — bridging both platforms for hybrid organizations without replacing either.

Zenphi connects Mailchimp to Google Workspace workflows via its integration layer. A campaign content approval completed in a Zenphi workflow triggers a Mailchimp audience update or campaign send. New contacts added to a Google Sheet from a form submission are synced to a Mailchimp audience as part of the same workflow. Campaign events in Mailchimp can trigger Google Workspace follow-up actions — logging engagement data to Sheets, sending Gmail notifications to sales, or creating follow-up tasks.

Zenphi has first-class native Twilio SMS actions running inside Google Workspace-centric workflows. Google Workspace workflow events — a form submission, an approval completion, a deadline approaching — can trigger a Twilio SMS notification to the relevant person or team. Twilio inbound SMS received via webhook can trigger Zenphi workflows that log the message to Google Sheets, route it for response, or create a task. SMS as part of a governed operational workflow, no custom code required.

Zenphi connects SendGrid to Google Workspace as a named workflow step. A Zenphi workflow event — an approval, a form submission, a document completion — can trigger a SendGrid transactional email with the exact data from the workflow inserted into the template. SendGrid delivery events (bounces, unsubscribes) received via webhook can trigger Zenphi workflows that update Google Sheets records or create follow-up tasks.

Zenphi has first-class native Airtable actions running inside Google Workspace-centric workflows. A new Google Form submission creates an Airtable record with the correct fields populated. An Airtable record update triggers a Google Docs document generation, a Gmail notification, or an approval workflow. Airtable records can be read, created, and updated as named steps in Zenphi workflows, with the same conditional logic, approval routing, and audit logging applied to every action.

Zenphi connects Okta to Google Workspace as workflow steps. Okta webhook events trigger Zenphi workflows that create Google Workspace accounts, assign OUs and groups, provision Drive folders, and send welcome emails — all as a governed sequence. Google Admin Console events can trigger Okta actions as part of an offboarding workflow that spans both identity platforms. Every cross-system identity action is logged with a complete audit trail.

Zenphi connects SAP to Google Workspace as a workflow step via its HTTP/REST action layer. An approval workflow completed in Gmail can update an SAP purchase order. A SAP-generated event can trigger a Google Workspace document generation and notification sequence. For organizations running operational processes that span both SAP and Google Workspace, Zenphi provides the workflow orchestration layer without requiring a full SAP integration project.

Zenphi connects Oracle to Google Workspace operational workflows via its HTTP/REST action layer. Google Workspace workflow events — approvals completed in Gmail, forms submitted, documents generated — can trigger Oracle API calls that update records in Oracle ERP. Oracle events received via webhook can initiate Google Workspace workflows for approvals, document generation, or notifications. Full audit logging of every cross-system action taken.

Zenphi connects NetSuite to Google Workspace via its API integration layer. An AP approval workflow in Gmail triggers a NetSuite invoice update. A Google Form submission creates a NetSuite record. A NetSuite event triggers a Zenphi workflow that generates a Google Docs report, sends a Gmail notification, or logs data to Google Sheets. Field-level control over exactly what data flows to NetSuite and under what conditions. Every action logged.

Zenphi connects MySQL to Google Workspace workflows as a named database action step. Google Workspace workflow events can query MySQL for data (looking up a customer record, checking a value, reading a configuration), write records to MySQL (logging an approved transaction, recording a completed step), or update MySQL fields based on Google Workspace approval outcomes. MySQL query results are available as structured data objects in subsequent workflow steps — no database-level scripting required.

Zenphi connects MongoDB to Google Workspace workflows via its database action layer. Google Workspace workflow events — form submissions, approval outcomes, document processing results — can write structured data to MongoDB collections. MongoDB documents can be queried as part of a Zenphi workflow, with the query result driving routing decisions, document generation, or notification content. Full audit logging of every database action taken by the workflow.

Zenphi connects BigQuery to Google Workspace workflows as a first-class step. Scheduled Zenphi workflows can query BigQuery and route results to Google Sheets, generate Google Docs reports from the query output, or trigger approval workflows based on queried values. Google Workspace workflow events can stream data to BigQuery for analysis. For data teams and operations leaders who need BigQuery insights to drive Google Workspace processes — or Google Workspace events to feed BigQuery — Zenphi provides the orchestration layer between both.

Zenphi connects Azure AD to Google Workspace operational workflows via its HTTP/REST layer. Azure AD user provisioning events received via webhook can trigger Zenphi workflows that create corresponding Google Workspace accounts, assign the correct OU and Google Groups, set up Drive folders, and send welcome communications. Google Workspace Admin Console deprovisioning events can trigger Azure AD account suspension as part of a unified offboarding workflow. For IT teams in hybrid Microsoft/Google environments, Zenphi provides the operational workflow bridge between both identity systems.

get started today

Every system your process touches — connected in one workflow

In 30 minutes we'll take a specific process from your team — one that currently involves Google Workspace, an approval, and at least one external system — and map it as a Zenphi workflow. You'll see exactly how the integration points fit.