Integrations forward events that another system already produces into a GraphJSON collection. They are the fastest path for provider data; the logging API remains the better choice for a product-specific event contract.
Open Integrations to connect a provider.
Available integrations#
| Provider | What arrives | Typical uses |
|---|---|---|
| Segment | Track and identify payloads sent to the destination | Product analytics and unified event pipelines |
| Stripe | Stripe event objects delivered by webhook | Revenue, subscription, invoice, and payment analytics |
| Vercel | JSON log drain entries for selected projects | Errors, traffic, function activity, and deployment diagnostics |
Each integration writes into a collection, so the same Samples, visualizer, SQL, dashboard, embed, and alert workflows apply.
For another provider, place a custom-source webhook adapter you control between the provider and GraphJSON. The adapter verifies authenticity, minimizes the payload, preserves the source event ID and occurrence time, and handles retries.
Integration or logging API?#
Choose an integration when:
- the provider already emits the facts you need
- keeping the provider payload is useful
- setup speed matters more than a small, curated schema
Choose the logging API when:
- the event represents a product concept the provider cannot know
- you want a stable, minimal contract
- you need control over identity, names, units, and event time
- the provider payload is too large or sensitive
Many teams use both. Stripe can supply raw billing events while application code emits a small subscription_activated event aligned with product logic.
Choose a custom adapter when the provider signs webhooks, retries deliveries, or emits a payload that must be normalized before GraphJSON receives it.
Plan the collection#
Provider payloads can be wide and change over time. Give each integration a dedicated collection unless its events genuinely share the same retention and analysis workflow with existing data.
Recommended examples:
segment
stripe_events
vercel_production_logs
After connecting:
- trigger a real test event
- open Samples
- identify the fields you actually need
- set a deliberate retention policy
- build a small reconciliation query
Then follow Operating managed integrations to define ownership, health signals, schema-drift detection, reconnect behavior, incident response, and a safe disconnect plan.
Security and privacy#
Provider payloads may contain customer or operational data you did not intend to copy.
Review what the source sends, limit event selection at the provider when possible, and avoid forwarding secrets or payment card data. Apply a retention period appropriate to the payload.
Disconnect unused integrations promptly. If an integration-generated destination URL is exposed, contact hi@graphjson.com.