Webhooks

Send buyer and company activity from your target lists to your own endpoint as they happen.

Push buyer and company activity from your target lists to any endpoint you control — no login or authorization step required.

Before you begin

• An endpoint URL that can receive POST requests
• At least one Target List with contacts or companies in it
• Admin or Marketer access to your 1eyeᴬᴵ workspace

For this guide, we’ll use Snowbricks as the example workspace.

Field	Example
Company	Snowbricks
Endpoint URL	https://api.snowbricks.io/hooks/mainv1
Workspace admin	Matt Bru
Admin email	[e-mail]

Configure the destination

Unlike HubSpot, Salesforce, and Slack, Webhooks doesn’t use a login step — you configure it directly at the Destination node.

Step 1: Open the Destination node

If the webhook isn’t configured yet, the node shows:

Webhooks · Not Ready

Step 2: Enter your Endpoint URL

Enter the URL that should receive events.

Field	Example
Endpoint URL	https://api.snowbricks.io/hooks/mainv1

Step 3: Send a test event

Select Send test event to confirm your endpoint is reachable.

✓ Test event sent successfully

Step 4: Choose Push Behavior

Option	Description
Identified Buyers Only	Send the event first time a buyer is identified.
Identified Buyers with New Signals Only	Send the first time a contact is identified.
Identified Buyers with All Signals	Send every time a new signal is captured.

Step 5: Add Custom Headers (optional)

Add key/value headers to include with every request, such as a signing secret.

Key	Value
X-1eye-Signature	whsec_9f2a7c4b8e1d

Select + Add More to add another header.

Step 6: Save

Select Save Changes. The Destination node updates from Not Ready to Active.

Monitor pushed records

From the Console, filter Webhook pushes by All / Pushed / Pending / Failed. Select a contact to see the exact payload sent to your endpoint.

Disable Webhooks

• Open the workflow and select the Destination node
• Select the menu next to the Active status
• Select Disable

Disabling stops any workflows using Webhooks as a destination until you re-enable it. Events already sent to your endpoint remain there.

Best practices

Verify your endpoint before saving Use Send test event to confirm your endpoint responds correctly before turning the destination on.

Use a signing secret Add a Custom Header like X-1eye-Signature so your endpoint can verify events actually came from 1eye.

Match push behavior to your use case Use Identified Buyers Only for low-volume alerting, or Identified Buyers with All Signals for full activity streaming.

Watch the Console after changes After editing your endpoint or push behavior, check the Console to confirm events are landing as Pushed, not Failed.

Troubleshooting

Issue	What to check
Send test event fails	Confirm the Endpoint URL is correct and reachable, and that your server isn’t blocking the request.
Node shows Not Ready	Confirm the Endpoint URL is filled in and a test event has been sent successfully.
Events failing in the Console	Check your endpoint’s response — a non-2xx response is recorded as Failed.
Custom Header isn’t being sent	Confirm both the Key and Value fields are filled in before saving.

FAQ

Does Webhooks use OAuth like HubSpot or Salesforce?

No. Webhooks doesn’t require a login or authorization step — you configure it directly with an Endpoint URL and, optionally, Custom Headers.

What happens if I disable Webhooks?

Workflows using Webhooks as a destination stop sending events until you re-enable it. Events already sent to your endpoint remain there.

Can I send to more than one endpoint?

Each Destination node sends to a single Endpoint URL. To send to multiple endpoints, add a separate Destination node for each one.

Next step

Go to Destinations to build your first Webhooks workflow.