Before launch

Use this checklist whenever you connect a new lead source or destination. The goal is to prove the full path from source submission to dashboard, team alert, and destination record.

  • Source platform has the correct webhook URL, secret, form, page, campaign, or bridge configuration.
  • InstaChime workspace has the correct alert channels, routing rules, owners, and CRM webhook destinations.
  • The destination account has the required permissions to create contacts, leads, rows, or messages.
  • You have a known test lead identity that can be recognized in the dashboard and in the destination.

Run the test

  • Submit a lead from the source platform or from the closest available source test tool.
  • Confirm the InstaChime capture response returns 200.
  • Confirm the lead appears in `/app` with correct name, email, phone, source, campaign, and message.
  • Confirm live alert delivery for each configured channel.
  • Confirm outgoing webhook delivery for each CRM, sheet, or automation destination.
  • Submit the same test lead again and confirm duplicate handling behaves as expected.
  • Temporarily send one destination to a failing URL and confirm retry state is visible in `/integrations`.

Evidence to keep

  • Timestamp of the source submission.
  • InstaChime lead ID.
  • Alert delivery row status.
  • Destination delivery row status and HTTP response.
  • Destination record ID, sheet row number, message ID, or automation run ID.
  • Screenshots or logs from the source, InstaChime, and destination.

Document the integration before testing

  • Write down the source platform, account ID, campaign or form name, destination app, owner, and expected lead volume.
  • Record the exact webhook URL, bridge URL, Zap URL, Make URL, or API endpoint being used.
  • Record the secret or token storage location without writing the secret value itself in the document.
  • List every required field that must arrive in InstaChime and every required field in the destination.
  • Decide what counts as success before the test starts: dashboard lead, alert message, CRM record, sheet row, and delivery history row.

Use one traceable test identity

  • Use a unique name such as `InstaChime Test May 27` so the lead is easy to find.
  • Use an email alias you control, for example `admin+instachime-test@example.com` if your mailbox supports plus addressing.
  • Use a phone number that can receive the alert if SMS, WhatsApp, or voice is part of the path.
  • Put the source name in the message field when the vendor allows custom message text.
  • Avoid using real customer data during setup tests.

Verify timing and retry behavior

  • Capture the exact time the source submission was made.
  • Confirm the lead arrives in the InstaChime dashboard within the expected response window.
  • Confirm the first alert is sent to the intended channel.
  • Confirm the destination receives the lead and returns a successful response.
  • Temporarily break one destination URL in a controlled way, send one test, then restore the URL and confirm retry visibility.

Sign off the integration

  • Save the source submission screenshot or source event ID.
  • Save the InstaChime lead ID.
  • Save the alert delivery row status.
  • Save the destination record ID, sheet row number, message ID, Zap run, Make run, or CRM ID.
  • Confirm an owner can explain how to pause, rotate, or replace the integration later.