AI agent for erp consultants
Integration Setup Verification Agent
Confirm that data flows correctly in both directions before an integration is marked complete.
What it does
The setup screen says Connected, but three weeks later the customer says half their orders are missing in the product. This agent verifies each integration with test records instead of trusting the status. It creates test records in the source system, checks that they arrive on the other side and compares the fields, such as names, amounts, dates and currency. It also checks the reverse direction if the integration is two-way. It lists mismatches, for example a date arriving in the wrong format or a status that is not mapped. After the specialist or the customer's team fixes the mappings, it retests with fresh records. It also tests an edge case such as a record with special characters. The specialist approves marking the integration complete. Edge case: the customer's system is a live production system, so the agent uses only test records and marks them for cleanup.
How it works
Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.
Read the steps as a list
- Integration shows Connected
- Create test records in the source system
- Read the records that arrive on the other side
- Compare each field with the field mapping
- Do all required fields match for every test record?If not: list the mismatches, propose mapping fixes and send fresh test records after the fix. Back to step 2.
- Test edge cases such as long text, special characters and empty fields
- Do the edge cases arrive intact?If not: report the failing cases and retest after the fix. Back to step 6.
- Test the reverse direction for two-way integrations
- Mark test records for cleanup
- Specialist approves marking the integration completeThe agent waits here for your OK.
- Verification report
How it decides
A field passes if the value that arrives equals the sent value after format rules. The integration passes only when all required fields in all test cases match.
- Always test with at least five records, including one with special characters
- Fail the integration if any required field differs after format rules
- Test the reverse direction whenever the integration is two-way
- Use only records labeled as test and remove them after the check
Make it yours
Every agent is a starting point. You choose these settings for your own situation.
- Number of test records (default 5)
- Required fields to compare
- Edge cases to include
- Directions to test
- Cleanup rule for test records
What keeps you in control
It always asks you first
- Specialist approves marking the integration complete
- Specialist approves any test in a customer's live system
Hard limits
- Never use real customer records for tests
- Never mark an integration complete without approval
It stops when
- Done: all test cases pass in both directions
- Stop: the customer does not allow test records in their system
Set it up
We guide you through the set-up, step by step
Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.
- One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
- The agent then walks you through connecting your own data, one source at a time
- A downloadable copy with the flow chart, the rules and the full guide