Skip to main content
Chat GPT Image Aug 5, 2026, 02 51 06 AM
New to Fourgent? See How It Works for the full walkthrough of what happens after you hit send.
Onboarding agent takes your description, asks any clarifying questions it needs, then begins connecting your apps and building out the integration spec. The quality of your prompt directly affects the quality of your integration. The tips below help you get to a live, accurate integration faster, with fewer back-and-forth questions.
You don’t need to be technical. Onboard doesn’t expect API knowledge or field names, just a clear description of your business workflow.

​
1. Name both apps explicitly

Don’t say “my CRM” or “our accounting tool.” Name the actual app.
“When a deal closes, create an invoice in our accounting software.”Which CRM? Which accounting tool? Onboard has to ask before it can start.

​
2. Be specific about the trigger

The trigger is the exact event that starts your integration. “Sync my CRM” is a goal, not a trigger.
“Sync my HubSpot deals to Xero.”Sync when? All deals? What condition?

​
3. Describe what data should move

If you know which fields matter, say so.
“When a deal closes in HubSpot, create an invoice in Xero.”Onboard doesn’t know which deal fields to put on the invoice.

​
4. Include your conditions upfront

If the integration should only fire for certain records, say that from the start. Conditions added after the fact require the integration to be updated and redeployed.
“When a deal closes in HubSpot, create an invoice in Xero.”Fires for every closed deal in every pipeline.

​
5. Say what should be skipped

Skip conditions prevent your integration from firing on records it shouldn’t touch.
“Sync new Shopify orders into Visma e-conomic.”What about test orders? Cancelled orders? Free orders?

​
6. Describe what happens in edge cases

What should your integration do when something unexpected happens, a missing field, a record that already exists?
“When a new person is added in Pipedrive, create a contact in HubSpot.”What if the contact already exists in HubSpot?

​
7. One integration per chat

Each workflow chat builds one integration. Combining multiple workflows in one description creates ambiguity.
“When a deal closes in HubSpot create an invoice in Xero, and also when a Shopify order comes in create a record in Visma e-conomic.”Two separate integrations in one prompt. Onboard may miss details for one or both.

​
Quick Reference Checklist

Before you hit send:
  • Named both apps explicitly
  • Defined the exact trigger
  • Described what data should move
  • Included any conditions upfront
  • Said what should be skipped
  • Covered the obvious edge cases (duplicates, missing fields)
  • Kept it to one integration per chat
You don’t need every answer before you start. Onboarding agent will ask follow-up questions for anything it needs. These tips just help you give it a strong starting point, which means fewer questions and a faster build.