How to use Signal Webhooks
Send the signals your agents find to any tool you run, automatically on every agent run or manually for signals you select.
Prerequisites
- You are on a Teams or Teams Pro plan with Firmable.
- Your organisation admin has configured a signal webhook endpoint.
What are Signal Webhooks?
Signal Webhooks send the signals your Signal Agents find to a destination of your choice, automatically. Each time an agent runs, the signals it surfaces are posted to a customer-defined HTTPS endpoint, where they can flow into automation platforms like Zapier, Make, or n8n and from there into virtually any downstream tool, including Slack, Google Sheets, sequencers, and custom systems.
This is separate from Signal Agent Actions, which push signals into HubSpot and Salesforce as native tasks and notes. Signal Webhooks are how you reach any tool beyond those native CRM integrations.
Setting up a signal webhook endpoint (admin)
Before signals can fire, an organisation admin must configure the endpoint where signals will be delivered.
- Navigate to Settings.
- Click Integrations in the left sidebar.
- Locate the Webhooks section and add the HTTPS endpoint URL for signal delivery.
- Save the endpoint and store the signing secret, which can be used to verify deliveries on the receiving side.
This is the same page where company and people webhook endpoints are managed. No signals will fire until a valid endpoint is configured here.
Enabling Signal Webhooks for an agent
Signal Webhooks are toggled on or off per agent, not globally. This means an admin can have the endpoint active but only send signals from the agents that are relevant.
- Open the agent you want to configure.
- In the agent setup, locate the Signal Webhook toggle and switch it on.
- Save your changes.
Agents created before Signal Webhooks was available continue to run as normal. Edit any existing agent and switch the toggle on when you are ready.
How signals are delivered
Automatic delivery: each time an agent runs with its Signal Webhook toggle on, up to 100 signals are automatically posted to the configured endpoint.
Manual delivery: from the agent's runs view, select specific signals and fire them to the endpoint on demand. This is useful for ad-hoc plays or signals from a high-volume run that you want to send selectively.
Note: the 100-signal cap applies per agent run. For agents that surface large volumes of signals, use targeted agent settings and manual selection to keep the most relevant signals flowing downstream.
What can I do with signals once they reach my endpoint?
From your endpoint, signals can be routed through an automation platform into almost any tool. Common examples include:
- Alerting your team in Slack when a key account has a leadership change or new hire.
- Adding signals to a Google Sheet for tracking or reporting.
- Enrolling contacts into a sequencer when a buying trigger fires.
- Feeding a custom internal system that has no native Firmable integration.
For tools that do have native integrations, Signal Agent Actions (which create tasks and notes inside HubSpot and Salesforce) and Signal Webhooks can be used together, with your CRM covered natively and everything else reached via the webhook.
Frequently asked questions
Can I push signals like new hires or job changes via webhook?
Yes. Signal Webhooks are specifically designed for this. Signals your agents find, including new hires, leadership changes, intent spikes, and role moves, fire to your endpoint automatically on each agent run or when you manually select and fire them.
How many signals fire automatically per run?
Up to 100 signals per agent run. For larger volumes, use manual selection from the runs view to fire specific signals to the endpoint.
What is the difference between Signal Webhooks and Signal Agent Actions?
Signal Agent Actions create native tasks and notes directly inside HubSpot and Salesforce. Signal Webhooks send signals to any HTTPS endpoint, which is how you reach tools that do not have a native Firmable integration. Many customers use both.
Do I need to reconfigure existing agents?
No. Existing agents are unaffected and continue to run as normal. Edit any agent and switch the Signal Webhook toggle on when you want it to start sending signals.
Does changing the endpoint in settings affect all agents?
Yes. The endpoint is configured at the organisation level. All agents with their Signal Webhook toggle on will send to the same endpoint.
We hope this article has helped you get signals flowing into the tools your team works in every day. If you have any questions, contact us at support@firmable.com.