HTTP Request
Call an external HTTP API from the workflow.
The HTTP Request action sends an outbound HTTP call with configurable method, URL, headers, content type, and optional JSON body with variable placeholders.
When to use
- Integrate external systems (CRM, billing, custom APIs).
- POST webhook payloads built from variables.
- Fetch or mutate remote state between Pingmee steps.
Configuration
| Field | What it does | When to use |
|---|---|---|
| Method | GET, POST, PUT, PATCH, DELETE | Match API contract |
| URL | Request URL (text input) | Endpoint address |
| Content Type | application/json, application/x-www-form-urlencoded, text/plain, text/html, or none | Set when body needs a MIME type |
| Headers | Name/value rows; add or remove rows | Auth tokens, custom headers |
| Body | Raw body text (POST/PUT/PATCH only) | JSON or text; use {{n}} placeholders |
| Add variable | Appends next {{n}} placeholder to body | Dynamic JSON segments |
| Beautify | Formats body as JSON when valid | Clean up JSON before save |
| Template variable bindings | One tree picker per {{n}} in body | Map placeholders to upstream data |
| Description | Canvas note | Document endpoint purpose |
Body placeholders
- Placeholders look like
{{1}},{{2}}, … - Each index can bind to a Variable or Expression from connected nodes.
- Beautify shows a toast error if the body is not valid JSON.
Headers
Enter Name and Value for each header row. Remove all rows if you do not need custom headers.
Flow behavior
- Body section appears only for POST, PUT, and PATCH.
- Default new nodes: method
GET, empty URL. - Output: Single edge to the next step.
Examples
GET status
- Method → GET.
- URL →
https://api.example.com/status. - Add Authorization header if needed.
POST JSON with customer id
- Method → POST, Content Type →
application/json. - Body:
{"customerId": "{{1}}", "event": "workflow"}. - Bind
{{1}}to customer id from the trigger.