Action nodes - Default

Action nodes do general jobs in a workflow. They can call an outside system, redirect a visitor, work with dates, and store values for later nodes to use.

Add a node in the Workflows builder with Add Node. Then pick one of the nodes below.Many fields accept data from the trigger or an earlier node. Type {{ to open the variable picker.

Send to Webhook

Sends an HTTP request to a URL you choose. Use it to push data to a system Default does not connect to natively. The endpoint must be reachable on the public internet over http or https. Default blocks requests to localhost and to private or internal network addresses. Request

Field	What it does	How to use it
Request Type	The HTTP method.	Choose POST, GET, PUT, PATCH, or DELETE. GET requests have no body.
Request URL	The endpoint Default sends the request to.	Enter the full URL, for example `https://api.example.com/leads`. Type `{{` to insert a value if the URL needs one.
URL Parameters	Query-string values added to the URL.	Add a key and value, for example `source` and `default`. Default appends them as `?source=default`.
Headers	Request headers.	Add a key and value for each header the endpoint expects. If you send a body and set no `Content-Type`, Default sends `application/json`.

Authorization controls how Default authenticates. Choose one option:

None
API Key: you set an API Key and a Header Name. The default header name is X-API-Key.
Token: you set a Bearer Token.
Basic: you set a Username and a Password.

Body has two tabs. Fields builds the body from key and value pairs. JSON lets you write the raw JSON yourself. Type {{ to insert a value. Default sends a body only with POST, PUT, PATCH, and DELETE.

Prepare response fields before the first run

Example response tells Default which fields the endpoint can return. Add one when a later node needs a value from the response. For example, a billing platform can return a customer ID after the webhook creates a customer. Add that response shape now, then use the returned ID in a later CRM node. You do not need to send real customer data before you can finish the workflow.

An example describes the expected response. It does not send the request, test your authorization, or guarantee the live response.

Enter the endpoint

Choose Request Type and enter Request URL. Generate becomes available after you enter the URL.

Generate an example

Select Generate. Default reads the public API documentation for the request method and URL. The draft can take up to 60 seconds.

Send to Webhook node with a generated Paddle customer response and its structure preview

Review the draft

Check the field names, nesting, and value types. Edit the JSON if the response you expect is different.Default marks a generated example with AI-generated draft — review it before relying on it. The note clears after your first edit.If Default cannot find a documented response, it leaves Example response unchanged. You can paste valid JSON instead.

Use a returned field

Add Create Variable after Send to Webhook. Enter billing_customer_id for Variable name. For Value, select Response, data, then data.id.

Create Variable node with data.id available from the generated webhook response

The run log warns you if the live response has a different shape. Update Example response when the endpoint changes so later field choices stay accurate. After the request runs, later nodes can use the response body and the HTTP status code. To act on the result, add a Multi-Branch node and compare the status code. Default cancels a request that takes longer than 30 seconds. Default does not follow redirects.

Redirect

Sends the visitor’s browser to a URL. Useful at the end of a form-driven workflow.

Field	What it does	How to use it
URL to Redirect to	Where to send the visitor.	Enter the destination, for example `https://example.com/thank-you`.
URL Parameters	Query-string values added to the URL.	Optional. Add a key and value, for example `name` set to the lead’s first name from an earlier node.

Date Transformer

Shifts a date forward or backward and saves the result for later nodes. You can add more than one transform. For each transform:

Field	What it does	How to use it
Input date	The date to shift.	Pick a date or date-and-time value from the workflow, for example the meeting’s scheduled time.
Direction	Shift earlier or later.	Choose Before or After.
Unit	The unit of time.	Choose Minutes, Hours, or Days.
Amount	How much to shift.	Enter a number, for example `1`.
Output name	What to call the result.	Enter a name, for example `reminder_time`, to reference it in later nodes. Use letters, numbers, and underscores.

For example, set Input date to the meeting time, Before, Days, and Amount 1. Set Output name to reminder_time to get the day before the meeting for a reminder node.

Create Variable

Defines one or more named variables you can reuse in later nodes. Each variable’s value can reference data from an earlier node or be a fixed value you type in.

Field	What it does	How to use it
Variable name	What to call the value.	Enter a name, for example `campaign_name` or `meta.source`. Dot notation is allowed.
Value	The value to store.	Pick a value from an earlier node, or type a fixed value such as `Q3 inbound`.

Select Add variable to define another one in the same node. For example, set campaign_name to a fixed value. Set lead_score to a value an enrichment node produced. Then reference both in a later CRM or notification node.

​Send to Webhook

​Prepare response fields before the first run

​Redirect

​Date Transformer

​Create Variable

Send to Webhook

Prepare response fields before the first run

Redirect

Date Transformer

Create Variable