Investigations call any endpoint of your providers' APIs
Investigations read the whole provider API
Investigations can call any read endpoint of the provider APIs you have connected, for teams whose evidence sits somewhere Polylane has no dedicated tool for.
What changed
Investigations can now read any endpoint of the GitHub,
Cloudflare,
AWS,
Vercel,
Fly.io,
Render,
Datadog,
Honeycomb,
Axiom and
Sentry APIs. When no dedicated tool covers what an investigation needs, it calls the provider's API directly with the access you already gave Polylane. The same access has since reached more integrations, among them
Supabase,
Neon,
Linear and
GitLab.
Small responses
API responses are trimmed before the investigation reads them. Link fields are dropped, long strings are cut and long lists are capped at 50 items, so one large response leaves room for the rest of the evidence.
Every fix has its own page
Each fix opens on its own page, with an overview and a timeline of what happened from the investigation to the pull request.
Why it matters
Every provider exposes more than a set of built-in tools can cover. When an investigation can call the provider's own API with the access you already granted, a question about an unusual setting or a rarely used product gets answered from the source, instead of stopping at "I can't see that".
How to use it
- Connect the provider under Settings > Clouds or Settings > Integrations.
- Ask a thread something the built-in tools do not cover, for example "Which
GitHub Actions workflows on
acme/apifailed on main this week?". - Open the tool call in the thread to see the endpoint it called and the trimmed response.
Related
Improvements
-
Cloudflare Investigations can search and read Workers traces
-
Cloudflare Pipelines streams, pipelines and sinks join the context graph, with checks on decode errors, user errors and writes to sinks