Webhook Trigger

Complete user guide

What is the Webhook Trigger?

The Webhook Trigger starts your workflow when an external system sends data into Trigify via an HTTP request / Webhook. Think of it as a doorway that lets other apps and tools push information into Trigify to kick off automated workflows, run enrichments, create signals and trigger downstream actions automatically.

When to Use Webhook Triggers

Use webhook triggers when you want external systems to programmatically start Trigify workflows.

Common scenarios:

  • Your CRM pushes new lead data into Trigify

  • Sending profile URLs to get enriched form Clay

  • Your product sends user behavior events (signups, feature usage, upgrades)

  • Form submissions from your website trigger follow-up workflows

  • Third-party tools like Zapier, Make, or custom apps send data to Trigify

Setting up a Webhook trigger

Simple 3-step process:

  1. Add a Webhook Trigger to your workflow in Trigify

  2. Copy the unique webhook URL generated for that workflow

  3. Send data to that URL from any external system using an HTTP request

When the request is sent, Trigify immediately fires the workflow and processes the incoming data - including enrichment, signal detection, and follow on workflows.

How it works:

Step 1: Add the Trigger

  • Create a new workflow or edit an existing one

  • Click on your current trigger or "Add Trigger"

  • Select "Webhook" from the trigger options

Step 2: Get Your Webhook URL

  • Trigify automatically generates a unique webhook URL for your workflow

  • Copy this URL - you'll need it to configure your external system

Step 3: Configure Your External System

  • Go to the external app or tool you want to connect

  • Find their webhook or integration settings

  • Paste your Trigify webhook URL

  • Configure what data should be sent.

What Data Can You Receive?

The webhook trigger accepts whatever data the external system sends.

Inside your workflow, you can:

  • Access all fields and values in the webhook payload

  • Use that data for enrichment, filtering, and branching logic

  • Pass enriched or transformed data back out to other tools

For example, a post URL sent into Trigify can be enriched for engagement, then sent back to Clay with updated data.

Example Use Cases

Sales & Outreach Automation

Detect role or company changes from your CRM, enrich the contact, create a signal, and automatically trigger sales outreach or add the contact to outbound sequences.

CRM Hygiene & Signals

Schedule CRM workflows to send outdated records into Trigify, enrich them, detect changes, and keep both person and company records up to date.

Engagement & Data Pipelines

Send post or profile URLs into Trigify, enrich engagement data (likes, interactions), and send the results back to Clay for further workflows.

Troubleshooting

If your webhook workflow isn't firing:

  1. Check the trigger is turned on - Make sure your workflow is active

  2. Verify the webhook URL - Ensure the external system is sending to the correct URL

  3. Confirm the external system is connected - Check that the integration is still active

  4. Check the Logs - Review workflow logs for any errors

  5. Test the webhook - Many external systems have a "test webhook" feature to verify the connection

Key Differences from Other Triggers

Webhook triggers are fully programmatic. Instead of Trigify deciding when to run, external systems decide when something important happened and notify Trigify instantly.

Webhook

When an external system sends data into Trigify

New Post Created

When a new social media post matches your saved search

Signal Created

When a custom signal you've defined is generated

Scheduled

On a recurring schedule (daily, weekly, etc.)

Manual

When you manually run the workflow

Best Practices

  • Use descriptive workflow names so you know which webhook URL belongs to which integration

  • Test before going live - Always send a test webhook to verify your workflow works correctly

  • Monitor your logs - Check workflow execution logs regularly to catch any issues early

  • Secure your webhooks - Only share webhook URLs with trusted systems

Need help setting up a specific webhook integration? Let Jarvis AI know what system you're connecting and it can provide more specific guidance!