HTTP Request

The HTTP Request node lets you make custom API calls to any external service directly from your Trigify workflows. It is your escape hatch for connecting to any tool that has an API, even if Trigify does not have a native integration for it.

Why Use the HTTP Request Node?

Trigify has native integrations for the most popular tools, but your stack might include something unique. The HTTP Request node lets you call any REST API, so you can push data to internal tools, trigger webhooks, query external databases, or connect to any SaaS product with an API.

How to Configure

Configuration Options

Setting

Description

Method

GET, POST, PUT, PATCH, or DELETE

URL

The full API endpoint URL

Headers

Key-value pairs for HTTP headers (authentication, content type, etc.)

Query Parameters

Key-value pairs appended to the URL as query string parameters

Body

Request body for POST, PUT, and PATCH methods (JSON format)

Output Variables

Variable

Description

result

The response body from the API call

statusCode

The HTTP status code (200, 201, 400, etc.)

success

Boolean indicating whether the request succeeded

Example: Sending Data to a Custom Webhook

Example: Calling a Third-Party API

Example Workflow

Pro Tips

Pro tip: Use the HTTP Request node to connect to tools that do not have native Trigify integrations yet. If it has an API, you can connect it.

Pro tip: Chain multiple HTTP Request nodes to build complex integrations. For example, first GET data from one API, then POST it to another.

Warning: Be careful with API keys in headers. Never share workflows that contain hardcoded API keys. Use environment variables or secrets when available.

Note: The HTTP Request node supports any REST API. For GraphQL APIs, use a POST request with the query in the body.