Inbound URL capture
Receive data directly from apps, automations, shortcuts or scripts through Conduit's custom URL scheme.
Custom URL routing for macOS and iOS automation
Receive once. Repurpose everywhere.
Conduit accepts a single inbound URL payload, captures its parameters, and lets you send that same information onward to one or more apps through their own URL schemes.
Built for people who use Shortcuts, launchers, URL schemes, callbacks and custom app automations.
-
One payload, many actions
Turn a single capture into notes, tasks, references, archives or linked follow-up actions.
-
Template-driven mapping
Use tokens, fallbacks and date formatting to translate source fields for each app.
-
Callbacks and chaining
Capture success, failure and returned item links, then trigger follow-up routes.
Conduit
A routing layer for your app automation
Core workflow
1. Receive an inbound URL
Capture title, text, content, tags, dates, source links and any other parameters.
2. Map fields into saved routes
Build app-specific URLs with tokens like {{title}}, {{tags}} and {{source}}.
3. Dispatch to one or many apps
Trigger routes manually, by short name, or after callback results.
Mapping
Fallback values, empty-field omission and flexible date formats
Callbacks
Success, failure, returned messages and created item links
Why Conduit works
A practical bridge between app URL schemes.
Many apps can receive information through URL schemes, but they rarely agree on parameter names, date formats, callback behaviour or what a useful payload should look like. Conduit sits in the middle, translating one captured payload into reusable routes.
It is especially useful when a source app only supports one custom export URL. Point that single URL at Conduit, then choose or automate whichever destination app should receive the data next.
Main features
Everything you need to turn app URLs into reusable workflows.
Reusable route builder
Create, edit, duplicate, reorder, import and export routes for any app that accepts URL actions.
Multi-destination dispatch
Reuse the same active payload across multiple saved routes, each with its own parameter structure.
Payload history
Keep received payload sessions available so older captures can be reselected, inspected and reused.
Single export URL bridge
More than one destination from apps that only allow one custom URL.
Some apps only let you configure a single custom export URL, which normally locks that export to one destination. With Conduit, that one URL can point to Conduit instead, giving you a flexible handoff point for sending the captured data to whichever route or app makes sense at the time.
Route building
Translate one payload into the shape each app expects.
Conduit routes are built from a destination URL plus parameter mappings. Tokens resolve against the active payload, so each app can receive the same source data in its own preferred format.
Routes can also use short names, callback URLs and follow-up actions, making them useful both for manual dispatch and larger automation flows.
Token mapping
Use values like {{title}}, {{text}}, {{content}}, {{tags}}, {{date}}, {{source}} and {{fullURL}} inside destination parameters. Any parameter included in the incoming payload can be referenced.
Fallbacks and clean output
Add fallback values such as {{tags|inbox}} and automatically omit empty values from final outbound URLs.
Flexible dates
Format incoming dates for task apps, journaling flows and scheduling actions, with fallbacks like today, today+7 or today-1.
Callback-aware workflows
Generate success and failure callbacks, capture returned item links, and reuse those links in later routes.
Built for real automation work
Useful when the same information needs to move through several tools.
Conduit is for writers, researchers, PKM users and productivity enthusiasts who collect information in one place, then need to reshape it for notes, tasks, references and archives.
Note capture
Send incoming titles, excerpts, links and tags to Drafts, Bear, Ulysses, DEVONthink, Anecnote or other note tools.
Task creation
Turn the same capture into tasks with destination-specific titles, notes, due dates and scheduling fields.
Research and references
Route article URLs, summaries, excerpts and tags to read-later, archive, reference and writing systems.
Chained automations
Create a note first, receive its item link back, then create a linked task or reminder automatically.
Example flow
Trigger once, then let the chain continue.
A Conduit workflow can begin with one manual action, then continue automatically as each route receives the information it needs from the previous step.
That makes callback-aware app automation feel less like a collection of fragile one-off shortcuts and more like a reusable routing system.
Step 1
Send the URL payload to Conduit
Manually trigger the first action from a shortcut, launcher, share sheet or source app. Conduit captures whatever parameters are sent, commonly including title, text, content, tags, date or source URL.
Step 2
Create the note automatically
A saved route maps the payload into your note app's URL scheme. You can trigger it manually from within Conduit, or have it run automatically when the inbound URL includes the route parameter.
Step 3
Receive the callback and item link
If the destination app supports callbacks, Conduit can receive confirmation that the note was created and capture the URL for the new note item.
Step 4
Trigger the follow-up task
Conduit then runs a follow-up route that creates a task in your todo app, including a direct link back to the note that was just created.
Support and next steps
Build a routing layer around the apps you already use.
Conduit makes app-to-app automation easier to inspect, adjust and reuse. Instead of rebuilding one-off shortcuts for every destination, define the translation once and let routes handle the rest.
Short-name triggering
Launch one or more routes automatically from an inbound payload.
Import and export
Back up, restore, migrate or share route sets as JSON.
Apple platforms
Use the same core routing model across Mac, iPhone and iPad.
Transparent payloads
See what came in, preview what will go out, and revisit past sessions.