Skip to main content
You’re in. Here’s what happens from here. Fourgent builds your integration from a plain-language description of your workflow. You don’t write code, and you don’t need a technical spec. You just need to know how your workflow should actually run, including the messy parts.
If you can explain your workflow to a new coworker, you can explain it to Fourgent. That’s really the whole skill required here.

​
Before you start

Admin or API access

Access to the apps you want to connect. Onboarding agent will tell you exactly what it needs when it needs it.

A workflow you know well

Ideally your messiest one. Fourgent is built to handle exceptions, so bring the workflow that broke the last tool you tried, not the simplest one.
You don’t need diagrams, field mappings, or a written spec. That’s what the onboarding agent is for.

​
What happens when you start

Your integration moves through four agents. Each one starts automatically when the one before it finishes, and you can watch every step happen in the chat as it goes.
1

Onboard

You’ll be asked about your systems, your data, and your edge cases—the same questions an experienced integration specialist would ask. This is the only stage where you’ll provide most of the input. Be as specific as you can: use real field names, actual exceptions, and real-world “what happens when X” scenarios.
2

Build

Fourgent builds the integration to match exactly what you described. Your fields, your rules, your edge cases. Nothing generic.
3

Test

Your integration is run against real data from your own apps before it ever touches production. If something fails, it gets fixed here. Deployment only happens after every test passes.
4

Deploy & Watch

Your integration goes live. Fourgent keeps watching it afterward: retrying failures, logging every run, and flagging you if anything changes.
Nothing happens behind closed doors. Every question, decision, test, and deployment is visible in the same conversation.

​
Common questions when you’re starting out

You don’t need to. Onboarding agent is designed to surface the ones you haven’t thought of yet by asking about them directly. Answer what you know; it’ll ask about the rest.
Yes. Nothing ships until it passes testing, and nothing goes live without your go-ahead at deployment stage.
Nothing is final until you approve deployment. Getting a detail wrong during onboarding isn’t a mistake you’re stuck with.

​
Built for teams automating real work

Whether you’re connecting CRM, accounting, eCommerce, support, or internal systems, Fourgent builds integrations around your exact workflow—not generic templates.
Have a unique workflow? Fourgent builds around your business, your rules, and your edge cases—not the limitations of pre-built connectors.

​
Built for the apps you’re using for your business

HubSpot

CRM & Marketing

Pipedrive

CRM & Sales

Shopify

eCommerce

Xero

Accounting

Visma e-conomic

Accounting

Fortnox

Accounting

Your own APIs

Custom integration

​
Known beta limitations

Editing a workflow after it’s deployed isn’t available yet. If something needs to change, flag it before deployment rather than after.

​
Start with your hardest workflow

The workflow that made you leave your last tool is the one worth testing first

That’s where the difference shows up fastest, for you and for Fourgent.

​
Security & Compliance

Security & Compliance

Fourgent is GDPR compliant. Your data is handled securely at every stage, from the moment you connect your apps to every sync that runs in production.