Zoho Creator is where UAE companies build the apps their ERP does not cover. We design the API layer that connects those apps to your ERP, partners and devices, with authentication, error handling and logs.
Zoho Creator integrates in both directions: outbound, Deluge scripts call external REST APIs with invokeUrl and stored Connections that manage OAuth tokens; inbound, external systems use the Creator REST API or custom APIs published from the app. UAE businesses should add logging, retries, alerts and a shared ID between Creator and ERP records so failures and mismatches stay visible.
Zoho Creator API integration in the UAE is usually needed once a Creator app becomes business critical. A contractor's site inspection app, a facility management company's work-permit tracker, a trading company's container costing tool or a clinic's referral portal starts as a standalone app in Zoho Creator. Within months it needs to read customers from the ERP, push approved costs to accounting, accept data from a supplier portal or receive readings from a scanner.
Zoho Creator supports integration in both directions. Outbound, Deluge scripts call external REST APIs using invokeUrl and stored Connections that manage OAuth tokens or API keys. Inbound, external systems use the Creator REST API to read and write records in forms and reports, or call custom APIs you publish from the app. Within Zoho, apps such as CRM, Books and People are reached through built-in Deluge integration tasks.
This page focuses on the API layer. If the integration you need is messaging, see Zoho Creator WhatsApp integration. For general principles across any ERP, read ERP API integration in the UAE.

The products we configure, integrate and support on projects like this one.
Product names and logos are trademarks of their respective owners and are shown only to identify the software we implement.
We are often asked to rescue Creator apps where integrations were added quickly. The issues repeat.
An API key or refresh token is pasted into a Deluge script. When the developer leaves or the key rotates, the integration stops and nobody knows where the key lives.
invokeUrl calls fail on timeouts or validation errors but the form submission still succeeds. Records exist in Creator that never reached the ERP, and finance finds out at month-end.
Scripts that call an API per record run fine in testing but exhaust daily API call limits during bulk updates. Integrations stop on the busiest day.
Creator records and ERP records are matched by name instead of an ID. A renamed customer or project breaks the link and creates duplicates.
API calls are sent to the wrong regional Zoho domain, or the external system is on a different data centre than expected. Authentication fails with errors that look unrelated.
Example: a site variation request approved in Creator and posted to the ERP, with the status returned.
One shared database: every step updates stock, finance and reports in real time.
The exact objects depend on your app. These rows reflect common UAE use cases.
| Data | Direction | Trigger / frequency | Notes |
|---|---|---|---|
| Customers, suppliers, projects | ERP to Creator | Scheduled or on lookup | Store the ERP ID in Creator as the matching key |
| Approved costs, requests, timesheets | Creator to ERP | On approval | Posted as a draft document for finance review where it affects the ledger |
| Status and document numbers | ERP to Creator | In the API response or by callback | Lets users see the ERP reference without logging in |
| Partner submissions | External system to Creator | On demand via REST or custom API | Validate input; reject incomplete payloads with clear messages |
| Attachments and photos | Creator to ERP or storage | On submission | Check file size limits on both sides |
| Device or scanner readings | Device middleware to Creator | Event-driven | Batch where volumes are high to stay within API limits |
| Reference data (cost codes, tax codes) | ERP to Creator | Daily schedule | Avoid letting users type codes that the ERP will reject |
| Error log entries | Within Creator | On every failure | A log form with payload, response and retry count |
API call limits and features depend on your Zoho Creator plan; we size the design against your plan's limits.
We pick the simplest method that can be monitored and maintained by your team.
We treat a Creator integration like any production integration: documented, secured and monitored.
We write down each endpoint, payload, matching key, owner system and error behaviour before writing Deluge. This becomes the handover document.
We create Connections for each external system with the minimum scopes needed, so tokens are refreshed by Zoho and never pasted into scripts.
Every call writes to a log form with request, response and status. Failed calls are retried on a schedule and escalate to a named person after repeated failures.
We test with month-end volumes, batch where possible, and confirm the design stays within your plan's API limits.
We deploy through Creator's environments where your plan supports them, and provide ongoing support through our Zoho Creator development team or train your in-house Creator admin.
APIs move data out of the controlled app, so design choices matter. Confirm tax and legal points with your advisors.
Know which Zoho data centre your account uses and where the external system stores data. Share only the fields needed, in line with the UAE Personal Data Protection Law and any sector rules.
Where Creator data creates invoices or bills in the ERP, tax codes should come from the ERP's master data, not free text, so VAT returns stay accurate.
If a Creator app originates billing data, the ERP must still produce PINT AE-compliant invoices through an Accredited Service Provider once e-invoicing applies to you; check the latest MoF and FTA guidance.
Keep the integration log and Creator's record history so you can show who approved what and when it reached the ERP.
General information, not tax or legal advice. Rules change; confirm current FTA, MOHRE and Ministry of Finance guidance with your advisor.
The value is reliability, which matters more as more of the business runs through Creator.
Every Creator record carries the external ID and status, so you can see what reached the ERP and what did not.
Logged errors and alerts replace the month-end surprise.
Connections, a log form and a written specification mean another developer can support it.
Batching and limit-aware design keep integrations working as volumes rise.
We configure the system for the rules UAE businesses report against, and test it before go-live.
General information, not tax or legal advice. Confirm current requirements with the FTA, MOHRE or your advisor. See all UAE compliance guides.
On-site workshops in Dubai, Abu Dhabi and Sharjah, and remote or on-site delivery across the Northern Emirates and free zones.
Official sources and references
Facts on this page were checked against these sources in October 2026. Rules change, so confirm current requirements before acting.
Still have a question? Our consultants are happy to help.
Ask an ExpertNew integrations should use the current Creator REST API version documented by Zoho, with OAuth 2.0. Older versions with auth tokens have been deprecated, so integrations built on them should be migrated.
Yes. You can publish custom APIs from a Creator app that run Deluge logic when called, or let the external system write directly to a form through the REST API. We add validation either way.
Creator is cloud based, so on-premise systems need an exposed, secured API or middleware that can reach them. We often use a small gateway or a middleware platform for this.
Zoho Creator applies API call limits by plan. We design batch syncs, cache reference data and avoid per-record calls in loops so normal operations stay within limits.
Yes. Creator can call any ERP with a REST API, including Odoo, ERPNext and Dynamics 365, through invokeUrl and Connections. The ERP side needs an integration user with the right permissions.
Zoho Flow suits simple, low-volume flows between supported apps and is easier for non-developers. Complex logic, high volumes or strict error handling are usually better in Deluge or a custom API, as covered in our Zoho integration services.
Related Solutions
Related Industries
Related ERP Platforms
Send us the systems your Zoho Creator app needs to talk to and we will propose an integration design with security and monitoring built in.
Dubai, United Arab Emirates