Integrations

Review Stripe events beside Linear updates.

Check recorded payments and issue changes together when investigating an account question.

Connected activity

4 events from 2 sources
Sources

Stripe · Linear

  1. StripeRefund completed

    Event from this source

    Completed
  2. LinearLinear issue reopened

    Event from this source

    Created
  3. StripePayment succeeded

    Event from this source

    Recorded
  4. LinearBug fix completed

    Event from this source

    Completed
Activity feed

Activity from Stripe, Linear.

Sources connected in this workflow

2 sources connected

What enters Grondeo

What you can do with this connection

Billing and product records may both be useful when deciding what to investigate next.

Example events

  • Refund completed
  • Linear issue reopened
  • Payment succeeded
  • Bug fix completed
  • Account follow-up created

How to use it

Connect Stripe and Linear. Review recorded activity; configure Stripe webhooks if you need supported subscription events. Timing alone does not explain a billing change.

Important limitation

Available events depend on source configuration. Follow a source link when you need more detail.

Source eventRefund completed

Stripe 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

Stripe

Access required: A Stripe secret API key for polling, or permission to configure a Stripe webhook endpoint and its signing secret.

  1. Open Settings → Integrations → Stripe and choose API polling or webhooks.
  2. Test and save your API key, or configure the webhook destination in Stripe and save its signing secret in Grondeo.

Events you can review: Polling covers supported payment, customer, and refund events. Subscription and invoice events require webhook setup. Grondeo displays individual events; it does not calculate churn or explain why a customer cancelled.

Linear

Access required: A Linear API key with access to the projects you want to follow, or permission to configure a Linear webhook and its signing secret.

  1. Open Settings → Integrations → Linear and choose API polling or webhooks.
  2. For polling, enter and test your key, choose projects, and save. For webhooks, configure the destination and matching signing secret shown in settings.

Events you can review: Issue creation, closure, status updates, and comments. Available activity depends on the projects and connection method you configure.

Plan and history

These built-in sources are available on Free, within its two-integration limit. Each connected provider counts once; selecting multiple GitHub repositories does not add integrations.

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

Connect Stripe and Linear. Review recorded activity; configure Stripe webhooks if you need supported subscription events. Timing alone does not explain a billing change.

  1. 10m ago
    Stripe

    Refund completed

  2. 2h ago
    Linear

    Linear issue reopened

  3. 4h ago
    Stripe

    Payment succeeded

  4. Yesterday
    Linear

    Bug fix completed

  5. 2d ago
    Linear

    Account follow-up created

Best used for

Billing events

Product issues

Account follow-up

Churn review

Questions

Before you get started

Which plan do I need?

Free includes two integrations and seven days of searchable history. Starter includes five integrations; Pro includes eight and custom sources.

What should I expect from the feed?

Connect Stripe and Linear. Review recorded activity; configure Stripe webhooks if you need supported subscription events. Timing alone does not explain a billing change.

Get started

Start with the two tools you check most.