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

1. In your Trigify workflow editor, add an HTTP Request node.

2. Select the HTTP method (GET, POST, PUT, PATCH, or DELETE).

3. Enter the URL or cURL of the API endpoint.

4. Add any required headers (e.g., Authorization, Content-Type).

5. For POST, PUT, and PATCH requests, add the request body.

6. Optionally add query parameters.

7. Use Trigify variables from previous steps to dynamically populate any field.

Configuration Options

Output Variables

Example: Sending Data to a Custom Webhook

Webhook example

Example
HTTP Node
Copy
Method: POST
URL: https://your-app.com/api/webhook

Headers:
  Authorization: Bearer your-api-key
  Content-Type: application/json

Body:
{
  "name": "{{firstName}} {{lastName}}",
  "email": "{{email}}",
  "signal": "{{text}}",
  "source": "{{postUrl}}",
  "sentiment": "{{sentiment}}"
}

Example Workflow

Custom Clay Integration via HTTP Request

1. New Post (LinkedIn) — Detect relevant LinkedIn posts

2. Person Enrichment — Enrich the post author's profile

3. Email Enrichment — Find their email address

4. HTTP Request — POST the enriched data to your Clay table

Pro Tips