HTTP Request

The HTTP Request Node lets you connect Trigify to any platform with an API.

Unlike the Webhook Node (which sends a predefined schema), the HTTP Request Node allows you to build custom API calls with full control over the request method, headers, parameters, and body.

How the HTTP Request Node Works

When you make an HTTP request, you're essentially sending a structured message to another system's API. Here are the components you'll configure:

• Choose HTTP Method: This tells the API what type of action you want to perform. The most common methods are:

  • GET - Retrieve data from the API (like fetching a list of contacts from your CRM)

  • POST - Send new data to create something (like creating a new lead or contact)

  • PUT - Update existing data by replacing it completely

  • PATCH - Update specific fields of existing data without replacing everything

  • DELETE - Remove data from the system

• Set URL: This is the API endpoint address — basically the specific location where you're sending your request. Every API has documentation that tells you which URLs to use for different actions. For example: https://api.example.com/v1/contacts

• Configure Headers: Headers are like metadata tags that give the API important information about your request. The most common headers are:

  • Authorization - Your API key or token that proves you have permission to access the API

  • Content-Type - Tells the API what format you're sending data in (usually application/json)

• Add Query Parameters: These are optional filters or settings you add to the end of your URL.

• Define Body: For POST and PUT requests, this is where you put the actual data you're sending. It's usually formatted as JSON (a structured data format). For example, if you're creating a contact, your body might include their name, email, and company.

Setting Up an HTTP Request

Here's how to configure an HTTP Request node step by step.

1. Add the HTTP Request Node to your workflow.

2. Select your HTTP method. Choose based on what you're trying to do:

   • Use POST if you're creating something new (like adding a contact to your CRM)

   • Use GET if you're retrieving data (like fetching existing contact information)

   • Use PUT or PATCH if you're updating existing data

3. Enter the Request URL. This comes from the API documentation of the tool you're connecting to. It will look something like https://api.example.com/v1/contacts. Copy it exactly as shown in their documentation.

4. Add required Headers. Almost all APIs require an Authorization header with your API key. This usually looks like:

   • Header name: Authorization

   • Header value: Bearer your-api-key-here (or sometimes just your-api-key-here)
     
     Check the API documentation to see exactly how they want the authorization formatted. You'll also typically need to add:

     • Header name: Content-Type

     • Header value: application/json

5. (Optional) Add Query Parameters. Only needed for GET requests or when filtering data. For example, if you want to search for contacts by email, you might add a parameter like email=john@example.com.

6. For POST/PUT, add your Request Body. This is the actual data you're sending. It needs to be formatted as JSON. Here's an example of what a body might look like when creating a contact:

   { "name": "John Smith", "email": "john@example.com", "company": "Acme Corp" }

7. Save and test your workflow. Run the workflow to see if the HTTP request succeeds. The node will return the API's response, which you can use in later steps. Check the Logs to see if it worked!

Example Use Cases

• CRM Integration - POST enriched signal data into Pipedrive or Zoho CRM.

• Data Push - Send JSON payloads into Airtable, Notion, or a custom backend.

• Enrichment - Call Clearbit or People Data Labs via API to enrich a lead.

• Custom Alerts - Trigger events in tools like PagerDuty or Discord via API call.

Debugging & Logs

When working with APIs, sometimes requests fail due to authentication issues, incorrect payload formats, or rate limits.

• Open the Logs tab in your workflow editor.

• Each HTTP Request execution shows the response code and message returned by the API.

• Red nodes in the flow mean the request failed — click into the log to see the exact error.

• Common issues include:

  • Invalid API keys or missing authentication headers

  • Incorrect JSON structure in the request body

  • Rate limits from the external API

  • Request URL not matching the API endpoint