/ /

HTTP node

The HTTP node allows your workflow to send or receive data from any service with a REST API. This node supports common HTTP methods and provides flexibility for authentication, headers, and request and response handling.

The HTTP node can also be used to chain workflows by calling another workflow's API trigger endpoint, enabling modular automation design.

To configure an HTTP node:

  1. On the workflow canvas, add an action node named HTTP.

  2. Select the Auth Token connection you want to use. A valid connection appears as <name> ✓ Active.

    If no connection exists, go to Settings > Account and create a New token under Personal Access Tokens, then add the token here to create a new connection.

  3. Enter the URL endpoint where you want to send or fetch data. The URL can be static or dynamically built using reference outputs from previous nodes.

  4. Select the HTTP request method: GET, POST, PUT, or DELETE.

  5. Configure the authentication type for the request.

  6. Add any required headers. Headers carry metadata or context about your request (for example, Content-Type: application/json).

  7. (Optional) Define the request body if the method requires one (for example, POST or PUT).

  8. Provide a sample response (for example, a JSON payload) to generate the response schema. DevRev parses this schema automatically and makes the response fields available as named variables in downstream nodes. If no sample is provided, the raw response is available as an unparsed string.

Example: To fetch details about a DevRev object from an external system, configure an HTTP GET node with the external API endpoint and an Auth Token connection. Provide a sample JSON response such as {"id": "123", "status": "active"}. After the node runs, reference HTTP.response.status in a downstream condition node to branch the workflow based on the returned value.

For more information on using the HTTP node to trigger other workflows, refer to the API Triggers article.

📝 Note: The Code node is available for logic that cannot be expressed through the HTTP node or loop configuration alone.

Troubleshooting

  • Issue: HTTP node fails with an authentication error.

    Solution: Confirm that the Auth Token connection is active (it appears as <name> ✓ Active when valid). If the token has expired or been revoked, go to Settings > Account, generate a new Personal Access Token, and update the connection.

Was this article helpful?