Integrations
Connect Neatlogs to your tools — issue trackers, chat, source control, and other observability platforms.
Neatlogs connects to the tools your team already uses, configured under Settings → Integrations. There are three kinds: OAuth app connections, data imports from other observability platforms, and webhooks.
Looking to give Copilot and Neat Agent tools to use in chat — like reading a GitHub file or a Linear issue while you debug? That's a separate, per-teammate setup under Settings → Tools & MCPs. See Tools & MCPs.
App connections
Connect third-party apps via OAuth so Neatlogs can act in them — for example, opening issues from a detection or dispatching a fix to a repository.
| App | Used for |
|---|---|
| GitHub | Source control — required to dispatch Fixes suggestions that open pull requests |
| Slack | Notifications and alert destinations |
| Linear | Create and link issues |
| Jira | Create and link issues |
| Notion | Link and export context |
| Asana | Create and link tasks |
| Basecamp | Create and link to-dos |
GitHub and Linear also support connecting via a personal access token / API key instead of the full OAuth flow.
Importing from other platforms
Already running another observability platform? Import your existing data so it lives alongside your native Neatlogs traces. Imported traces are tagged with their source so you can tell them apart.
Start an import from Settings → Integrations, or from Experiments → Prompts → Import for prompt data. See Import Traces for the full walkthrough across Langfuse, LangSmith, Braintrust, Raindrop, and Arize Phoenix.
Imported traces carry an import-source marker (e.g. langfuse, braintrust) and are filterable in the traces list, so a migration never mixes imported and native data ambiguously.
Webhooks
Configure custom webhooks to deliver Neatlogs events to your own endpoints, with delivery history for debugging. Use these when you need to wire Neatlogs into systems that don't have a first-class app connection.
API keys
Trace ingestion is authenticated with a project API key, managed under Settings → API Keys. This is the key you pass to neatlogs.init() (or NEATLOGS_API_KEY) in either SDK, and the same key the wizard, Claude Code plugin, and MCP server use. Generate and revoke keys there.