Integrations
Bring custom events into Grondeo with webhooks.
Configure a Pro custom source and map the fields sent by your workflow.
Connected activity
4 events from 1 sourceWebhooks
- WebhooksInternal workflow completedCompleted
Event from this source
- WebhooksAgent run finishedRecorded
Event from this source
- WebhooksFeature flag changedRecorded
Event from this source
- WebhooksCustom account milestone recordedRecorded
Event from this source
Connected source
1 source connectedWhat enters Grondeo
What you can do with this connection
Internal tools can produce useful updates that a standard source integration does not cover.
Example events
- Internal workflow completed
- Agent run finished
- Feature flag changed
- Custom account milestone recorded
- Manual review completed
How to use it
Create a custom integration on Pro, configure its incoming webhook, and map the source payload to event fields. Test delivery before relying on it.
Important limitation
Available events depend on source configuration. Follow a source link when you need more detail.
Webhooks remains the system where the work happens.
Recorded updates appear in a consistent feed.
Follow the source link when it is available and you need more detail.
Connection guide
What you need to get started
Send custom events on Pro
- Create your account and add a custom integration.
- Choose Pro from billing, then choose the incoming webhook connection and map your payload fields to the event details.
- Configure your sending workflow using the endpoint and authentication settings in the app. Send an event and check its details in the feed.
Your workflow supplies the custom activity. This is separate from named agent access on Starter or Pro. Each custom integration counts toward your source limit.
To deliver activity from Grondeo to another system, use outgoing activity webhooks on Starter or Pro.
Plan and history
Custom incoming webhook sources require Pro. Each custom integration counts as one source.
Your plan sets the searchable history window: 7 days on Free, 60 on Starter, and 365 on Pro. Source APIs, permissions, and connection methods determine which events can be collected. A longer history window does not guarantee a complete backfill; webhooks collect events delivered after setup.
Compare plansIn the timeline
Inspect individual updates
Create a custom integration on Pro, configure its incoming webhook, and map the source payload to event fields. Test delivery before relying on it.
- 10m agoWebhooks
Internal workflow completed
- 2h agoWebhooks
Agent run finished
- 4h agoWebhooks
Feature flag changed
- YesterdayWebhooks
Custom account milestone recorded
- 2d agoWebhooks
Manual review completed
Best used for
Internal tools
Agent runs
Operational updates
Custom product events
Questions
Before you get started
Which plan do I need?
Custom JSON API and incoming webhook integrations require Pro.
What should I expect from the feed?
Create a custom integration on Pro, configure its incoming webhook, and map the source payload to event fields. Test delivery before relying on it.
Get started