Native Webhooks: Connector Events, Shaped for Your Agent

When a PR opens, a support ticket lands, or a deal stage changes, your agent should already be moving. But webhooks arrive in whatever shape each provider decided — some full-resource, many notification-only, all noisy, all under a different schema — so agents either burn tokens chasing context, wake up for events that don’t matter, or don’t fire at all. Native Webhooks closes the loop: StackOne ingests events from your connectors, runs them through the Falcon engine where you can filter, enrich, and reshape, then fans out to every subscribed destination.

What’s new

• Real-time events from your connectors - Receive events from GitHub, HubSpot, Notion, SmartRecruiters, Linear and more on one pipeline. No more per-provider registration, signature verification, or lifecycle plumbing to ship and maintain
• Filter events before they reach your agent - Drop draft PRs, Dependabot bumps, or CRM updates from sandbox accounts inline. On chatty sources like GitHub and HubSpot, this can cut agent triggers — and the token spend they burn — by an order of magnitude
• Hydrate notification payloads inline - HubSpot propertyChange events are change notifications: you get the object ID, property name, and new value, but not the rest of the deal state — owner, stage, amount, associations. Falcon fetches the full record and merges it in one step, so the webhook arrives fully hydrated
• Reshape to a shared schema - Normalize deal-update events from Salesforce, HubSpot, and Pipedrive into one shape before delivery. Your CRM agent handles one contract, not three provider quirks
• One or more destinations per event - Specify a single receiver or fan out to several — a calendar update can go to your note-taker, calendar sync, and CRM in one delivery. Destinations are configured at the project level, no duplicate subscriptions or rebroadcasting logic to maintain
• Per-account observability - Every delivery, retry, and failure is logged in the StackOne logs platform, scoped per connected account. Silent failures surface, and every agent trigger is traceable back to the event that fired it

Read the Native Webhooks docs