Test and publish a Zap safely

Where to start
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)

Before you begin

Agree the test data, expected result and responsible owner. A successful connection test is useful, but it does not prove that a trigger, mapping and destination action all work together.

Follow these steps

1. Write down one expected outcome using a unique fictional reference, for example ZAPIER-PILOT-PROPLIX-001.
2. Test the connection, then the trigger or search, then the destination action in the sequence shown by the approved app.
3. Open the saved CRM and destination records. Compare workspace, identifiers, fields and record counts.
4. Check the no-match, missing-field and duplicate cases your workflow may encounter. Use filters or review paths rather than creating a record on every error.
5. Publish only after the pilot is accepted. Set the responsible owner, normal review frequency and a clear pause procedure.
6. Review the first live runs and investigate mismatches before increasing the volume.

If something does not look right

If a write may have completed before a timeout, inspect the CRM or destination before replaying. Repeated test clicks are not a safe way to diagnose an uncertain write.

Fields, rules and limits

• Use fictional data that is recognisable as a test. A test action may still create records or send destination notifications.
• Keep passwords, authorisation codes, tokens and private customer details out of screenshots.
• Agree cleanup through the normal authorised record-management process after testing.

Questions and answers

Is the green connection test enough to go live?

No. Verify the complete trigger/search, mapping and destination workflow with a real test run.

Should I test on real customer information?

Use fictional or appropriately minimised test data unless your organisation has explicitly authorised another approach.

Do I need a separate test company?

A designated test workspace can help if one is available and authorised. Keep it clearly separate from production connections and never assume credentials or IDs transfer between companies.

How do I test a new-lead subscription?

Enable it as directed, create one uniquely labelled lead through the intended source workflow and verify one expected destination result.

How do I pause a problem quickly?

Turn off or pause the relevant Zap in Zapier, preserve the run references and check whether another Zap or subscription is also acting on the same source.

Can I increase volume immediately after one success?

Increase gradually after reviewing the first runs, task allowance, rate limits, duplicate controls and the team’s ability to investigate failures.

Useful next steps

• Map lead fields, sources and staff correctly
• Understand queued events, retries and delays
• Prevent duplicate leads and automation loops

Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.