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 source
Sources

Webhooks

  1. WebhooksInternal workflow completed

    Event from this source

    Completed
  2. WebhooksAgent run finished

    Event from this source

    Recorded
  3. WebhooksFeature flag changed

    Event from this source

    Recorded
  4. WebhooksCustom account milestone recorded

    Event from this source

    Recorded
Activity feed

Activity from Webhooks.

Connected source

1 source connected

What 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.

Source eventInternal workflow completed

Webhooks remains the system where the work happens.

Grondeo recordSource, timestamp, and event details

Recorded updates appear in a consistent feed.

Product reviewRead it beside what happened next

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

  1. Create your account and add a custom integration.
  2. Choose Pro from billing, then choose the incoming webhook connection and map your payload fields to the event details.
  3. 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 plans

In 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.

  1. 10m ago
    Webhooks

    Internal workflow completed

  2. 2h ago
    Webhooks

    Agent run finished

  3. 4h ago
    Webhooks

    Feature flag changed

  4. Yesterday
    Webhooks

    Custom account milestone recorded

  5. 2d ago
    Webhooks

    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

Choose a plan for your workflow.