> ## Documentation Index > Fetch the complete documentation index at: https://docs.cloudify.biz/llms.txt > Use this file to discover all available pages before exploring further. # Welcome to Fourgent > Four specialized AI agents. One chat. From idea to live integration — no code required. ## What is FourgentFourgent? Image Image The name says it all: **Four** a**gent**sThe name says it all: **Four** a**gent**s. Fourgent is an integration-building platform powered by four AI agents that work in sequence — each one handling a specific part of the process, then handing off to the next. You describe what you need in plain language. The agents figure out the restFourgent is an integration-building platform powered by four AI agents that work in sequence — each one handling a specific part of the process, then handing off to the next. You describe what you need in plain language. The agents figure out the rest. No code. No API docs. No setup scripts. Just describe the outcome, and Fourgent builds it. No code. No API docs. No setup scripts. Just describe the outcome, and Fourgent builds it. *** ## The Four AgentsThe Four Agents Every integration in Fourgent passes through the same four stages — one agent per stage, no gaps. Connects to your apps, discovers API endpoints, maps your data fields, and resolves edge cases before anything is built. Nothing is assumed. Nothing is left open. Writes the integration code — typed TypeScript shaped to your exact workflow. Not a template. Not a drag-and-drop config. Actual code your team can read and modify. Runs a full test suite built from your actual workflow — not generic unit tests. Every trigger, condition, and edge case gets validated before deployment is allowed. Ships the tested integration to production. Handles infrastructure, secrets management, CI/CD setup, and generates a handoff report for your team. Each agent activates automatically when the previous one finishes. You can watch the handoffs happen in real time in the chat. *** ## How It Works Every integration in Fourgent passes through the same four stages — one agent per stage, no gaps. Connects to your apps, discovers API endpoints, maps your data fields, and resolves edge cases before anything is built. Nothing is assumed. Nothing is left open. Writes the integration code — typed TypeScript shaped to your exact workflow. Not a template. Not a drag-and-drop config. Actual code your team can read and modify. Runs a full test suite built from your actual workflow — not generic unit tests. Every trigger, condition, and edge case gets validated before deployment is allowed. Ships the tested integration to production. Handles infrastructure, secrets management, CI/CD setup, and generates a handoff report for your team. Each agent activates automatically when the previous one finishes. You can watch the handoffs happen in real time in the chat. *** ## How It Works You interact with Fourgent through a single chat interface. Describe your integration — the agents take it from thereYou interact with Fourgent through a single chat interface. Describe your integration — the agents take it from there. Type what you need in plain language. A few examples: * *"When a deal closes in HubSpot, send a message to #sales in Slack."* * *"Sync new Shopify orders to our warehouse system every hour."* * *"Create a Jira ticket when a Zendesk ticket is marked high priority."* You don't need to know how the APIs work. Just describe the business outcome. The Onboarding Agent connects to your apps and maps the workflow. You'll see it surface questions only when it genuinely needs your input — things like field mapping decisions or edge case rules that only you can define. As it progresses, the right panel updates in real time across four views: * **Progress** — live status of each agent stage and test results * **Files** — the code files being generated * **Flow** — a visual map of your integration logic * **Mapping** — field-by-field data mapping between your systems Once the Testing Agent signs off, review the results and approve. The Deployment Agent handles everything from there — your integration is live and running. *** ## What You Can Build Type what you need in plain language. A few examples: * *"When a deal closes in HubSpot, send a message to #sales in Slack."* * *"Sync new Shopify orders to our warehouse system every hour."* * *"Create a Jira ticket when a Zendesk ticket is marked high priority."* You don't need to know how the APIs work. Just describe the business outcome. The Onboarding Agent connects to your apps and maps the workflow. You'll see it surface questions only when it genuinely needs your input — things like field mapping decisions or edge case rules that only you can define. As it progresses, the right panel updates in real time across four views: * **Progress** — live status of each agent stage and test results * **Files** — the code files being generated * **Flow** — a visual map of your integration logic * **Mapping** — field-by-field data mapping between your systems Once the Testing Agent signs off, review the results and approve. The Deployment Agent handles everything from there — your integration is live and running. *** ## What You Can Build If it involves two systems exchanging data or triggering actions, Fourgent can build itf it involves two systems exchanging data or triggering actions, Fourgent can build it. | Use Case | Example | | -------------------------- | -------------------------------------------------------------------------------- | | **CRM → Accounting** | Deal closes in HubSpot → invoice created in QuickBooks | | **Order Fulfillment** | New Shopify order → warehouse notified + Slack alert sent | | **HR Onboarding** | New hire in BambooHR → accounts provisioned in Slack, Jira, Google Workspace | | **Support Escalation** | High-priority Zendesk ticket → Jira ticket created + team alerted | | **Data Sync** | Customer records kept in sync between Salesforce and your database on a schedule | | **Finance Reconciliation** | Invoices matched against payments in your accounting tool every night | *** ## Who It's For Get systems talking to each other — without waiting on engineering. Ship reliable integrations faster. Skip the boilerplate, keep the code. Run complex, multi-app workflows that need to hold up in production. *** ## Tips for Best Results **Name the apps.** "HubSpot → Slack" is enough to start. The more specific you are, the faster the Onboarding Agent moves. **Describe the trigger precisely.** Instead of *"sync my CRM,"* say *"when a deal is moved to Closed Won in HubSpot."* **Include conditions and exceptions.** For example: *"Only for Enterprise accounts"* or *"Skip if the order is already fulfilled."* The more rules you define upfront, the fewer questions the agent needs to ask. | Use Case | Example | | -------------------------- | -------------------------------------------------------------------------------- | | **CRM → Accounting** | Deal closes in HubSpot → invoice created in QuickBooks | | **Order Fulfillment** | New Shopify order → warehouse notified + Slack alert sent | | **HR Onboarding** | New hire in BambooHR → accounts provisioned in Slack, Jira, Google Workspace | | **Support Escalation** | High-priority Zendesk ticket → Jira ticket created + team alerted | | **Data Sync** | Customer records kept in sync between Salesforce and your database on a schedule | | **Finance Reconciliation** | Invoices matched against payments in your accounting tool every night | *** ## Who It's For Get systems talking to each other — without waiting on engineering. Ship reliable integrations faster. Skip the boilerplate, keep the code. Run complex, multi-app workflows that need to hold up in production. *** ## Tips for Best Results **Name the apps.** "HubSpot → Slack" is enough to start. The more specific you are, the faster the Onboarding Agent moves. **Describe the trigger precisely.** Instead of *"sync my CRM,"* say *"when a deal is moved to Closed Won in HubSpot."* **Include conditions and exceptions.** For example: *"Only for Enterprise accounts"* or *"Skip if the order is already fulfilled."* The more rules you define upfront, the fewer questions the agent needs to ask. *** The Onboarding Agent will greet you and guide you from there. A few examples of how to start: * *"When a deal is marked Closed Won in HubSpot, create an invoice in QuickBooks."* * *"Sync new customer records from Salesforce to our PostgreSQL database every hour."* * *"Send a Slack alert to #finance whenever an invoice in QuickBooks is overdue by 7 days."* You don't need to know how APIs work. Just describe the business outcome. Watch the Onboarding Agent gather requirements, the Coding Agent write your integration, and the Testing Agent validate it — all in one view. Review the test results, approve, and the Deployment Agent handles the rest. Your integration is live. The Onboarding Agent will greet you and guide you from there. A few examples of how to start: * *"When a deal is marked Closed Won in HubSpot, create an invoice in QuickBooks."* * *"Sync new customer records from Salesforce to our PostgreSQL database every hour."* * *"Send a Slack alert to #finance whenever an invoice in QuickBooks is overdue by 7 days."* You don't need to know how APIs work. Just describe the business outcome. Watch the Onboarding Agent gather requirements, the Coding Agent write your integration, and the Testing Agent validate it — all in one view. Review the test results, approve, and the Deployment Agent handles the rest. Your integration is live. ## Next Steps Build and deploy your first integration step by stepstep by step. A deeper look at what each agent does and how they hand offA deeper look at what each agent does and how they hand off. Every app and API FourgentFourgent can connect to out of the box. CComplex use case? We'll help you scope it.