Connection guide
What you need to get started
GitHub
Access required: A personal access token for the repositories you want to follow. The app recommends a fine-grained token with read access to Metadata, Contents, Pull requests, and Issues. Authorize it for your organization if SSO is required.
- Open Settings → Integrations → GitHub and enter your token.
- Test the connection, select repositories, and save your changes.
Events you can review: Pull requests opened, merged, closed, drafted, or ready for review; issues opened, closed, reopened, or commented on; and published releases. A merged pull request does not confirm a deployment.
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.
- Open Settings → Integrations → Linear and choose API polling or webhooks.
- 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.
Stripe
Access required: A Stripe secret API key for polling, or permission to configure a Stripe webhook endpoint and its signing secret.
- Open Settings → Integrations → Stripe and choose API polling or webhooks.
- 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.
Zendesk
Access required: Your Zendesk base URL, account email, and API token, or permission to configure a signed ticket webhook.
- Open Settings → Integrations → Zendesk and choose API polling or webhooks.
- For polling, enter your URL, email, and token, then test and save. For webhooks, configure ticket payloads and the matching signing secret using the destination in settings.
Events you can review: Tickets created, updated, solved, commented on, assigned, or changed in priority. Review individual tickets alongside engineering activity when deciding what to investigate.
Plan and history
This workflow uses four sources, so choose Starter or Pro. You can try two of these tools on Free.
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