Integrations

Integrations connect Neatlogs to the tools your team works in. Alerts and new incidents post to Slack, an incident becomes a Linear or Jira issue, a fix goes to a coding agent against your GitHub repository, and traces from another observability platform land in a Neatlogs project. Use this page to decide which connection a workflow needs, where to connect it, and who can.

Know where each connection lives

Settings is split into Account, Organization, and Project sections. Organization and Project pages apply to the organization and project selected in the switcher.

Slack and Discord are the only shared connections. Linear, Jira, Notion, Asana, and Basecamp credentials belong to the person who connected them, so each teammate who pushes incidents to Linear or Jira connects their own account. If your role can't connect something, ask an organization owner or admin.

Example: route one failure through your tools

The checkout-assistant team wants three things when payment failures spike:

1. a post in #checkout-alerts when the payment-failure alert fires;
2. the resulting incident tracked as a Linear issue;
3. the fix sent to a coding agent against the checkout-service repository.

That takes Slack (organization), Linear (each engineer's own account), the GitHub App with checkout-service mapped to the project, and a Coding agents credential for the engineer who dispatches the fix. The sections below set up each piece.

Connect an organization integration

1. Open Settings → Organization → Integrations.
2. Find the app under All or Available, or search. Apps are grouped by category: Collaboration, Issue tracking, Knowledge, and Source code.
3. Select Connect. For Slack, Discord, Linear, Jira, Notion, Asana, and Basecamp you go to the provider to authorize Neatlogs. GitHub opens its own panel (see GitHub).
4. Approve access at the provider. Neatlogs returns you to the page with the notice "Authorization returned successfully. Check the connection status below to confirm setup is complete."
5. Confirm the row shows Connected, then select Manage to see the account under Connected as and any provider settings.

To remove a connection, select Manage, then Disconnect, and confirm. Disconnecting Slack or Discord stops every workflow in the organization that uses it.

Slack

Connect one Slack workspace per organization. Any organization member can connect or disconnect it, so agree on an owner before changing it. A workspace already connected to another Neatlogs organization can't be connected again until it is removed there.

Once Slack is connected:

Invite the Neatlogs app to any private channel you want it to post in. Connecting Slack here does not let Copilot or Neat Agent read channel history; that needs your own Slack connection in Tools & MCP.

Discord

An organization owner or admin connects the Discord server. Discord is not an alert destination. It adds the Neatlogs bot, which scans channels you enable and answers when mentioned:

• run /neatlogs enable in each channel the bot should scan;
• run /neatlogs disable to stop, or /neatlogs status to check a channel.

Like Slack threads, linked Discord threads corroborate incidents only after a project admin authorizes them under Issue evidence access.

Linear and Jira

Each engineer who exports work connects their own Linear or Jira account. Issues are created with that account's access in the tracker.

• On an incident with a fix, use Push to and choose Linear or Jira. The issue includes the root cause, evidence, recommended fix, linked traces, and a link back to Neatlogs. See Create tickets and close the loop.
• Pushing doesn't change the incident's status, and status changes in Linear or Jira don't sync back. Update the incident yourself when the work ships.
• For Jira, Manage also offers a standalone Create Jira issue button.

Connecting Linear here is separate from connecting Linear in Tools & MCP, which lets Copilot read your Linear issues in chat.

GitHub

GitHub connects through the Neatlogs GitHub App, installed once for the organization. An organization owner or admin manages it; other members see "Ask an organization owner or admin to install the GitHub App."

1. In Settings → Organization → Integrations, select Connect next to GitHub, then Install Neatlogs GitHub App.
2. On GitHub, choose the account and repositories to grant. If your GitHub organization requires approval, Neatlogs shows Waiting for GitHub organization approval; after a GitHub owner approves, select Check approval status.
3. Back in Neatlogs, with the project selected, check the repositories this project may use. Turn on Allow pull request writes only for repositories where Neatlogs may open pull requests.
4. Select Save project access. Repeat for each project.
5. Choose a Repository access policy: Shared uses the App's permissions; Strict also checks each member's own GitHub permissions, and members authorize the App in Tools & MCP.

Copilot uses only repositories mapped to the current project, and a pull request is opened only when someone clearly asks for one. Disconnecting the App "immediately disables GitHub access for every project in this organization. It does not uninstall the App from GitHub."

Coding agents

Open Settings → Account → Coding agents to connect your own Claude Code, Codex, or Cursor credentials. They belong to your account in the selected organization; teammates connect their own. Cursor uses a Cursor User API Key. Repository access still comes from the GitHub App.

On an incident, Fix in offers Open in targets for your editor and Cloud Agent targets. Use the menu to check which cloud targets are enabled for your project. For Claude Code Routines configuration and session monitoring, see Long-running sessions. See Review and hand off a fix.

Trace imports

Open Settings → Project → Trace imports to bring traces from Langfuse, LangSmith, Braintrust, Raindrop, Phoenix, or Laminar into the selected project. Source credentials are shared by the organization and saved by an organization owner or admin; running an import into a project requires Project Admin on that project.

Follow Import traces for each source, and Troubleshoot imports if a job stalls or traces are missing.

Webhooks

Open Settings → Project → Webhooks and select Create webhook. Give it a name and an Endpoint URL, optionally a Signing secret so your endpoint can verify Neatlogs, and pick the events to send: alert firings, incident alerts, approvals, comments and mentions, prompt version changes, experiment results, the daily digest, and evaluation assignments.

After saving, use Send test event and check the delivery history under Settings & deliveries. Pause delivery stops sending without deleting the webhook. An alert rule can also deliver to one webhook. Creating webhooks requires Project Member or Project Admin.

Confirm the connection works

A connection is ready when:

• the row shows Connected and Manage shows the expected workspace or account;
• one real workflow succeeds end to end, for example a Send test from the alert's Configuration tab posts in the intended Slack channel, or Push to creates an issue in the right Linear team;
• for GitHub, the project's repositories are checked and saved;
• for webhooks, the Send test event delivery appears in the webhook's delivery history and your endpoint received it.

Troubleshoot

For OAuth failures, wrong accounts, and revoked access, see Troubleshoot connections and permissions.

Frequently asked questions

Do I need to connect Linear myself if a teammate already did?

Yes. Linear and Jira connections belong to the person who made them. Each person who pushes incidents connects their own account.

Does connecting Slack send alerts automatically?

No. An alert rule must have Slack turned on in its Response step, and new-incident posts need an Incident Slack channel in Settings → Project → Project notifications.

Can Discord receive alerts?

No. Alerts deliver in-app, by email, to Slack, and to one webhook per rule.

Does disconnecting my Linear or Jira account affect teammates?

No. It removes only your connection. Teammates who connected their own accounts keep exporting with them.

Where are SDK API keys managed?

Under Settings → Project → API keys. See Understand project keys.

Next step

Connect your own apps for Copilot and Neat Agent →