SI Back Office

Troubleshooting guide · updated 2026-10-10

A Zap runs, but fields are missing: trace the value from trigger to destination

Inspect one synthetic record through each step and separate missing input, transformation, permissions and destination validation.

Follow one value across the boundaries

Choose one authorised synthetic source record with known values. Check what the trigger provided, what each transformation returned, what the action sent and what the destination stored. A workflow marked successful is not enough to prove all intended fields were mapped.

  • Name the destination organisation, object and field.
  • Record whether the source value was absent, blank, transformed or rejected.
  • Do not export real lead or invoice payloads for an enquiry.

Read the step evidence

Zapier's retrieved troubleshooting article describes inspecting the affected step's response and outgoing request. Missing inputs may mean useful logs are absent. Distinguish an absent source field from a stale mapping, invalid format or account permission problem; those require different changes.

  • Compare field names and expected types, not just display labels.
  • Resolve expired access with the account holder without sending its credential.
  • Check the destination after a failure before assuming it contains no record.

Testing is not assumed to be a dry run

Do not assume a button labelled Test or Replay leaves connected systems unchanged. Agree a disposable destination and review the specific action's effects before invoking it. Lead creation, invoice creation and notification can have consequences even with made-up input. The operator needs written authority for the named test route.

  • Use a stable synthetic reference to identify created records.
  • Test the create-versus-update or duplicate rule.
  • Avoid bulk replay until reconciliation and recovery are agreed.

Prove the complete business record

Acceptance should show the required values in the intended target record, correct object/account mapping and a controlled missing-field case. Keep redacted before-and-after step evidence and any remaining exclusions. Credentials, client access and purchases are not part of first-contact diagnosis; scope is confirmed before private work.

Sources and limits

  • Zapier: action troubleshooting Checked 2026-10-10.
    • The retrieved official article describes inspecting failed steps, logs, response details and outbound requests.
    • Missing values, formatting, permissions, expired credentials and limits can cause action problems.