Send results to your tools
The five 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 on their own Destinations page, under Delivery in the project sidebar, rather than as tiles in the Add source picker. Each destination is a card. Its footer shows whether it is connected. A tracker or Notion card opens a sheet to connect or manage it; the Outbound webhooks card opens its own Webhooks page. A viewer sees only the connected cards.
There are three kinds, and five 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 | Notion | A brief as a page |
Every one of them is configured per project.
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 the Webhooks page's Deliveries tab and each endpoint's detail panel show 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.
Credentials are replaced by disconnecting and connecting again
No destination has an edit form for a credential that still works. 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. The one exception is a tracker whose credential the other tool has refused: its card reads Needs attention, and opening it offers a Reconnect form in place.
Where to see this in Adduce
- Destinations in a project's sidebar groups the cards as Issue trackers, Automation (outbound webhooks) and Publishing and chat (Notion), in that order.
- 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.