Test integrations without affecting customers
Use sandbox accounts, controlled recipients, test bookings, logs, and rollback steps for safer integrations.
Guide typeStep by step
Estimated time2 minutes
Best forAutomation
Integration testing should prove one connection at a time without charging customers, sending unwanted messages, or exposing credentials.
Prepare a safe test
- Create a fictional test booking that is clearly labeled as a demonstration record.
- Use an email address and phone number owned by your business.
- Select sandbox or test mode whenever the provider offers it.
- Record the current setting so it can be restored if the test fails.
Test one connection
- Open Integrations or the feature-specific integration panel.
- Enter credentials directly into the protected field. Never paste them into notes or screenshots.
- Use the smallest available connection test.
- Trigger one controlled action, such as a test email, SMS, route lookup, or sandbox checkout.
- Check Party Desk history and the provider log for the same timestamp and reference.
Move to production
- Remove demonstration records or keep them clearly excluded from reports.
- Replace sandbox credentials with production credentials only when testing is complete.
- Verify the production account, location, sender, number, endpoint, and permissions.
- Monitor the first live transaction and confirm the expected Party Desk update.
- Document the integration owner and credential-rotation procedure.
Stop immediately if a test reaches a real customer, creates an unexpected charge, or exposes a secret. Disable the workflow, preserve non-sensitive logs, and investigate before retrying.
