Send results to your tools
The six destinations Adduce can push to, what each one receives, when a push happens, and why nothing a destination holds ever comes back in.
A destination is a tool Adduce writes to. Sources read in; destinations only ever get written to, and nothing a destination holds is ever read back into a project.
A destination is not a source
A source is a tool Adduce reads on a schedule. A destination is a tool Adduce writes to when you ask it to, or when something happens in the project. The two never mix: a destination has no sync, no sync history and no backfill, and it produces no evidence.
That is why destinations sit in their own sections on Sources, below the connected sources, rather than as tiles in the Add source picker.
There are three kinds, and six destinations
| Kind | Destinations | What leaves Adduce |
|---|---|---|
| Issue trackers | Linear, Jira, GitHub Issues | One issue per theme, on your click |
| Outbound webhooks | Your own URL | Signed JSON when themes change or a brief is published |
| Publishing and chat | Notion, Slack | A brief as a page; answers and alerts in a channel |
Every one of them is configured per project except Slack, which is configured once for the whole workspace.
Issue trackers push a theme on your click
Connect Linear, Jira or GitHub once per project, and every theme gains a create-issue button. Pressing it sends that theme across: the verdict and its reasoning, the evidence and source counts, the strength and sentiment, up to five customer quotes, the related findings, and a link back to the theme.
Nothing syncs back. Closing the issue in your tracker does not change the theme, and the theme changing later does not edit the issue.
Outbound webhooks push events to your own service
Register an HTTPS endpoint and pick the events you want. Adduce then POSTs signed JSON when a theme is created, when a theme changes, or when a brief is published — no click, no schedule.
Each delivery carries an HMAC signature, and each endpoint has a delivery log showing what was sent and what came back.
Publishing sends a finished brief out as a document
Connect Notion, choose a parent page, and Publish to Notion on a brief creates a page under it: the summary, the problem, the proposed change, the scope, the assumptions, the open questions, the acceptance criteria, the success metrics and the source themes. Publishing again updates the same page.
Slack is the one destination that is not per project
The Slack app is connected once for the whole workspace, under Settings → Integrations → Slack. It carries two things: answers to questions asked of Adduce in a Slack thread, and proactive posts — digests, alerts and sync outcomes — into a channel you nominate.
Credentials are replaced by disconnecting and connecting again
No destination has an edit form for its credential. Disconnect, then connect with the new one. Disconnecting deletes the stored credential and removes the control it powered; work already created in the other tool is left exactly as it is.
Where to see this in Adduce
- Sources in a project's sidebar holds Issue trackers, Outbound webhooks and Publishing, in that order, below the sources list.
- A theme's own page holds the create-issue button, once a tracker is connected.
- A brief's own page holds Publish to Notion, once Notion is connected and a parent page is chosen.
- Settings → Integrations → Slack holds the workspace connection and its delivery targets.