Conduit overview and how to use it

Conduit is a routing utility that receives information through a conduit:// URL, stores the incoming payload, and lets you reuse that same data in other apps through saved outbound routes.

What Conduit does

• Receives URLs such as conduit://capture?title=Idea&text=Follow%20up.
• Extracts query parameters like title, text, content, tags, date, and source.
• Saves recent payloads in Payload History.
• Builds outbound URLs for apps such as Drafts, Bear, Anecnote, Ulysses, OmniFocus, and Things.
• Lets you create custom routes for any app that supports URL schemes or x-callback-url.

Sending data to Conduit

Use the inbound address conduit://capture and add your data as query parameters.

conduit://capture?title=Idea&text=Follow%20up

You can open this URL from Safari, Shortcuts, Drafts, Launcher, or any app that can open custom URL schemes.

Using Payload History

Each received URL is saved as a payload session. Select a recent payload to inspect its source URL and available parameters. Conduit keeps the most recent payloads so you can test routes without sending the same URL again.

Creating a route

1. Tap New Route.
2. Enter a display name, such as My Notes App.
3. Optionally add a short name, such as notes, for auto-triggering.
4. Enter the target app's base URL, such as drafts://create or things:///add.
5. Add parameter mappings. The output parameter is what the target app expects, and the template is the value Conduit sends.

Template tokens

Use double-brace tokens to reuse incoming payload values.

{{title}}
{{text}}
{{tags}}
{{date}}
{{source}}

For example, a route to a notes app might map:

title = {{title}}
text = {{text}}
tags = {{tags}}

Auto-running routes

If a route has a short name, include route=shortname in the inbound URL to run it automatically.

conduit://capture?title=Idea&text=Follow%20up&route=drafts

To run multiple routes from one payload, use routes=one,two.

conduit://capture?title=Idea&text=Follow%20up&routes=drafts,things

Callbacks and follow-up routes

If a target app supports callbacks, map {{callbackSuccessURL}} or {{callbackFailureURL}} into the callback parameter the target app expects. When a success callback returns, Conduit can record the result and optionally run a follow-up route.