Agents
Platforms
Solutions
Use cases
Resources
About Book a demo

Automation Pro by AI Hub

From a form to a finished process. No code.

Forms, workflows, automations and an AI Copilot, in one product.

One-time costUnlimited users

1Forms

Design any form. Drag, drop, publish.

  • 24 building blocks, including files and signatures
  • Show or hide fields with conditional logic
  • Publish with a close date or submission limit

2Workflows

A workflow for every easy process.

  • Start with a trigger, then add steps
  • Filter, branch into paths, set the rules
  • Test it live before you publish

3Automations

Automations for advanced processes.

  • Chain nodes on a visual canvas
  • Branch on rules, call APIs, add AI steps
  • Test each step, then watch it run

4AI Copilot

Describe it. Your AI Copilot drafts it.

  • Builds workflows from a plain description
  • Edits and explains your existing flows
  • Preview first. Nothing applies until you accept.

Runs on your own AI key. Automation Pro is fully usable with no AI switched on.

5Approvals inbox

One inbox for every approval.

  • Every request waiting on you, in one place
  • Approve, reject with a reason, or reassign
  • Undo an approval right after you make it

Built for processes that need a record.

Version history

Publish a version. Restore any earlier one.

Run logs and test runs

Every run logged. Test before you publish.

Roles and permissions

Admin, builder and member roles.

Export and import

Take any build with you as JSON.

Approvals with undo

Reject needs a reason. Undo straight after approving.

Clear failures

A failed run shows the step and the error.

Run it in the cloud (a Saudi cloud provider in KSA, or your own cloud account) or on-premise. On a Saudi cloud provider or your servers in KSA, your data stays in KSA.

Connects to the systems you run.

Your forms, workflows and approvals reach the tools your team already uses.

Through ready connectors or API

Microsoft

  • Dynamics 365
  • Microsoft 365Outlook, Teams, Excel
  • SharePoint
  • OneDrive
  • Active Directory

ERP & finance

  • SAP
  • Oracleincl. NetSuite
  • Odoo
  • Zoho
  • Qoyod
  • Daftra

Google & CRM

  • Google Workspace
  • Salesforce
  • HubSpot

KSA and GCC operations

  • WhatsApp Business
  • Foodics
  • Salla
  • Zid
  • Jisr
  • ZenHR

Trademarks belong to their owners.

How it works

From idea to running process in four steps.

  1. Design

    Build the form, workflow or automation. Or ask the AI Copilot for a first draft.

  2. Test

    Run it with test data. Check every step before anyone else sees it.

  3. Publish

    Publish a version when it is ready. Earlier versions stay in history.

  4. Run and monitor

    Runs, approvals and failures appear in one place.

See it in 90 seconds.

Forms, workflows, automations and the AI Copilot, in one short film.

Automation Pro by AI Hub

Questions buyers ask.

Yes. Automation Pro connects through ready connectors or API, including Microsoft 365, Dynamics 365, SAP, Oracle, Odoo, Salesforce, HubSpot, Google Workspace and WhatsApp Business. Most systems with an API, webhooks or an MCP server can be connected. Where a ready connector does not exist, we build the integration.

No. You build on a visual canvas with forms and steps. People who want more can add code or call an API.

You describe what you need in plain words. The Copilot builds workflows from your description, and it can edit and explain the flows you already have. It shows a preview, and nothing is applied until you accept it. It runs on your own AI key, and Automation Pro is fully usable with no AI switched on.

Automation Pro runs in the cloud (a Saudi cloud provider in KSA, or your own cloud account) or on-premise. On a Saudi cloud provider or on your servers in KSA, your data stays in KSA. You bring your own AI key.

A workflow suits an easy process: a trigger, then filters, paths and app steps. An automation suits an advanced one: a canvas with branches, API calls, AI steps and a test for each step. Forms collect the input for either.

Every change is published as a version, and earlier versions stay in history so you can restore one. Roles decide who can build, approve or submit. Every run is logged.