How to Test Your Integration

What You’re Verifying

After we deploy your integration, you should confirm that data is moving between systems correctly. This guide walks you through what to check and what to do if something doesn’t look right.

We test everything on our end before go-live, but you know your data better than we do. A quick verification from your side catches edge cases we might not anticipate.

Step-by-Step Verification

1. Trigger a Test Event

Create a real (or test) event in the source system. For example:

• Create a new contact in your CRM
• Move a deal to the next stage
• Submit a form
• Complete a job or invoice

Use data you’ll recognize — something like “Test Contact - [Your Name] - [Today’s Date]” so it’s easy to find in both systems.

2. Wait for Processing

Most integrations process within a few seconds to a few minutes. If your integration runs on a schedule (every 15 minutes, hourly), you’ll need to wait for the next cycle.

We’ll tell you the expected timing during handoff.

3. Check the Destination System

Go to the destination system and look for your test record. Verify:

• The record exists. It should appear within the expected timeframe.
• Field mapping is correct. Check that names, emails, amounts, dates, and custom fields all landed in the right places.
• Formatting is right. Dates should be in the expected format, phone numbers should look correct, currency values should have proper decimal places.
• Relationships are intact. If the integration should link a contact to a company or a deal to a contact, verify those associations exist.

4. Check Your Dashboard

If your integration includes a monitoring dashboard, log in and look for your test event. You should see it listed with a status of “delivered” or equivalent. See Understanding Your Dashboard for details on reading statuses.

5. Test an Update

Don’t just test creation — test updates too. Go back to the source system, change a field on your test record, and verify the change appears in the destination system.

6. Test Edge Cases

If you have time, try a few scenarios that are specific to your business:

• A record with missing fields (no email, no phone)
• A record with special characters in the name
• A large text field or note
• Whatever your team does that’s “unusual”

What to Do If Something Looks Wrong

Data Didn’t Arrive

1. Check your dashboard — is the event listed? If it shows “failed,” check the error message.
2. Wait a few more minutes — it may still be processing.
3. Confirm you triggered the right event type. For example, if the integration syncs on “deal stage change,” simply editing a deal’s name won’t trigger it.
4. Contact us with the specific record and timestamp so we can trace it.

Data Arrived but Fields Are Wrong

This is usually a mapping issue. Take a screenshot of the source record and the destination record, note which fields are wrong, and send it to us. These are quick fixes.

Data Arrived Late

Check whether the integration is event-driven (near real-time) or scheduled (runs on intervals). If it’s scheduled, a delay up to the interval length is normal. If it’s event-driven and consistently slow, let us know.

Common Issues

Test Data in Production

If you’re testing in a production system, remember to clean up test records afterward. We recommend using a naming convention that makes test records easy to find and delete.

“I Changed Something but Nothing Updated”

Some integrations only sync specific fields. If you changed a field that isn’t part of the mapping, no sync will trigger. Check with us about which fields are included.

Next Steps

• Learn to read your monitoring dashboard: Understanding Your Dashboard
• Review what to do when you need changes: Requesting Changes
• Learn more about how we work