Sign inStart free

Integrations

Read your Grondeo activity through the API.

Retrieve the activity feed or connect a named agent to account history through separate REST endpoints on Starter or Pro.

See plans and pricingView connection guide

Connected activity

3 events from 3 sources
Sources

GitHub · Linear · Stripe

  1. GitHubPull request merged

    Event from this source

    Merged
  2. LinearIssue updated

    Event from this source

    Updated
  3. StripePayment received

    Event from this source

    Recorded
Activity feed

Activity from GitHub, Linear, Stripe.

Connected source

3 sources connected
GitHubConnectedLinearConnectedJiraAvailableStripeConnectedZendeskAvailableGranolaAvailableAPIsAvailableWebhooksAvailable

Read collected activity

What you can do with this connection

An internal workflow may need access to the activity already collected in Grondeo.

Example events

  • Pull request merged
  • Issue updated
  • Payment received

How to use it

On Starter or Pro, use the activity API to retrieve the feed. For agent workflows, create a named agent key with separate scopes and use the Agent REST API to search activity, record actions, and update follow-ups. Custom JSON ingestion and incoming webhooks are a separate Pro feature.

Important limitation

The activity feed API retrieves events. Named agents use separate REST routes and scopes to record actions and update follow-ups. Pro custom integrations handle importing from your own JSON endpoints.

Connection guide

What you need to get started

Choose an API path on Starter or Pro

  1. Create your account and connect a source.
  2. For the activity feed, create a key and retrieve recorded events. Configure outgoing webhooks if your system should receive updates.
  3. For agent workflows, create a named agent in Settings, choose its permissions, and use the Agent REST API or MCP server.

Named agents can record actions and update follow-ups. See agent access. To ingest events from your own JSON endpoint or incoming webhook, use a Pro custom integration.

Plan and history

Activity API access and outgoing activity webhooks require Starter or Pro.

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

On Starter or Pro, use the activity API to retrieve the feed. For agent workflows, create a named agent key with separate scopes and use the Agent REST API to search activity, record actions, and update follow-ups. Custom JSON ingestion and incoming webhooks are a separate Pro feature.

  1. 10m ago
    GitHub

    Pull request merged

  2. 2h ago
    Linear

    Issue updated

  3. 4h ago
    Stripe

    Payment received

Best used for

Activity feed

Agent REST API

Outgoing webhooks

MCP alternative

Questions

Before you get started

Which plan do I need?

The activity API, named agent access, and outgoing activity webhooks require Starter or Pro. Custom JSON sources and incoming webhooks require Pro.

How is the Agent REST API different?

The Agent REST API uses a named agent key with separate permissions for activity reading, action recording, follow-up reading, and follow-up updates. It can write agent actions and follow-up changes into account history.

Get started

Choose a plan for your workflow.

See plans and pricingAgent access