Webhook fix brief
Describe the failing automation in a way a developer can debug.
Generated brief
Common fixes
High-friction automation bugs that can start small.
Trace payload shape, node input/output, missing fields, retries, status codes, and final success evidence.
Check field object type, field key, custom values, workflow trigger context, and merge-tag output.
Fix bad merge tags, incorrect HTML in SMS, broken triggers, wrong appointment context, or stale contact data.
Map source parameters, booking origin, pipeline stage, contact fields, and notification text without losing attribution.
First checks
When a GHL custom field is missing.
- Confirm the field exists on the correct object, usually Contact, not Opportunity or a nested form-only field.
- Confirm the workflow step is using the exact custom field key or merge tag, not just the display label.
- Use a dummy contact or booking to test the trigger context before changing active automations.
Safe intake
No secrets needed for first review.
Start with redacted payloads, screenshots, field names, expected outputs, sample executions, and test contacts. Keep passwords, API keys, private customer lists, and payment data out of the first request.
Payment path
Use marketplace escrow or a direct fixed-scope deposit.
If the lead starts on Upwork or Freelancer, payment should stay inside that platform. Direct clients can request a clear scope first and then use paypal.me/AMEZQUITASALINAS or alejandro.amezquita@alumnos.udg.mx after the scope is agreed.