Home Glossary Zoho Flow Custom App Connector (Flow)
Zoho Flow

Custom App Connector (Flow)

A Custom App Connector in Zoho Flow is a user-defined integration that connects an app not natively supported by the platform by configuring that app's

Technical Term

A custom app connector removes the ceiling on what Zoho Flow can connect. If the app your business uses is not in the native app catalogue, a custom connector lets you define its API behaviour once, and then use it exactly like a built-in app in any flow you build.

How Custom App Connector Works in Zoho Flow

Within Zoho Flow, you can create a custom app connector by defining the app’s API base URL, authentication method (such as API key, OAuth 2.0, or Basic Auth), and individual API endpoints that serve as triggers or actions. For each endpoint, you specify the HTTP method, required parameters, and the response schema so the platform understands the data structure. Once built, the custom connector appears alongside native apps in the flow builder and can be used in any flow within your organisation.

When to Use Custom App Connector

Use a custom app connector when you need to integrate a proprietary internal system, an industry-specific SaaS tool, or a regional app that is not available in the Zoho Flow native catalogue. It is also appropriate when a native connector exists but lacks the specific endpoint you need, such as a less-common API operation for a supported app. Avoid building a custom connector for apps that are already natively supported unless the native connector is genuinely insufficient for your use case.

Key Considerations for Custom App Connector

Building a custom connector requires familiarity with the target app’s API documentation, including authentication flows and response formats. Test each endpoint definition with real API credentials before using the connector in production flows. If the target app changes its API, the custom connector definition must be updated manually; there is no automatic sync. Maintain internal documentation of the connector’s endpoint definitions and the flows that depend on it, so future changes can be assessed for impact before being applied.

India Example: A Pune-based manufacturing firm uses an in-house production tracking system with a REST API. Their Zoho Flow administrator builds a custom app connector for that system, defining endpoints for fetching production order status and updating completion records. This allows them to create flows that automatically update Zoho Inventory when a production order is marked complete, without any manual data entry.
What authentication methods does Zoho Flow support for custom app connectors?

Zoho Flow supports several authentication methods for custom connectors, including API key (passed as a header or query parameter), Basic Auth (username and password), and OAuth 2.0 (authorisation code flow). The exact options available may depend on your plan. OAuth 2.0 is recommended when the target app supports it, as it avoids storing static credentials and supports token refresh automatically.

Can I share a custom app connector with other users in my Zoho Flow organisation?

Yes. Custom app connectors built within your Zoho Flow organisation are available to all users in that organisation. They appear in the app selection alongside native connectors when building flows. If you manage multiple Zoho Flow organisations, the connector is specific to the organisation where it was created and must be rebuilt separately in other organisations.

Need help implementing this in Zoho?

Aaxonix is a certified Zoho implementation partner based in Pune. Architecture-first, no surprises.