Skip to content
English
More support Sign in
Go to patchretention.com
  • There are no suggestions because the search field is empty.

HTTP Request Action Block

Send data to an external system via an API call.

What's in this article

Summary

The HTTP Request block sends data to another system (webhook) and can map JSON responses back into the automation.

Important: The response payload size is limited (shown in the block).

When to use

  • Send leads to an external CRM or spreadsheet
  • Look up extra details from another system
  • Trigger a custom workflow in another tool

Common triggers that feed into this block

  • Contact Created (new lead/import) → send a quick welcome + next step
  • Check-In Finished (visit) → thank-you + upsell (classes, seasons, memberships)
  • Order Finished (purchase) → receipt/next steps + review request
  • Contact Updated (field/tag change) → react to a specific change (e.g., “Interested in seasons” = true)
  • Calendar Event (class/lesson booked) → reminders + no-show prevention
  • Membership Start/End → onboarding or win-back

How to set it up

  1. Choose the request method (GET/POST, etc.).
  2. Enter the request URL.
  3. Add headers if required (example: Authorization).
  4. Add parameters to send as JSON (SmartText allowed).
  5. Map JSON response fields into payload keys using Add Operation.

Best practices for businesses, programs, and classes

  • Keep payloads small and only store what you will actually use later.
  • Avoid sending sensitive data unless you must.

Tabs in this block

Editor

This is where you configure the block. After you change settings, save the block so the automation uses the updated configuration.

Stats

Stats populate after the block runs for at least one contact. For most blocks, Stats are mainly for quick troubleshooting (example: times triggered and last completed).

Task Log

The Task Log is the best place to troubleshoot a specific run. Each row is one task (usually one contact) that passed through this block.

  • Time: when the task ran
  • Run Duration: how long it took
  • Contact: click the person icon to open the contact profile
  • View Payload: click VIEW PAYLOAD to see all data passed through the automation for that task
  • Task ID: helpful for internal debugging and support

Warnings & Errors

  • Errors must be fixed before the automation can be enabled.
  • Warnings do not always block enabling, but they usually mean something is missing or risky.
  • If you see an error or warning banner, fix it in the Editor, then re-open the block to confirm it is cleared.