Apple Shortcuts
Pass prepared capture text into a named Apple Shortcut and continue its workflow there.
Set up Apple Shortcuts
- Create or choose a shortcut in Apple Shortcuts and test it there first.
- Make the shortcut use text input if you want it to receive your capture content.
- Enter its exact name as the default shortcut in Afterthought Settings, or review the named shortcut action before running it.
Start with one short capture in Classify & Review. Name the destination, check the prepared details, then send and inspect the result in the destination app.
How delivery works
Afterthought opens the named shortcut through Apple Shortcuts. An ‘Opened Shortcut’ result confirms the handoff, not successful completion of every action inside your shortcut. Shortcuts may ask for permissions or input.
What happens in Classify & Send?
Afterthought classifies the capture, applies configured routing and fallbacks, and prepares the adapter’s fields first. It then attempts the chosen route without entering classification review. Validation or incomplete setup can still stop delivery.
A draft, share sheet or app handoff can still open in this mode. You must finish any required confirmation there; “does not create directly” does not mean the route cannot be attempted by Classify & Send.
Multi-action bundles and corrected actions remain in review and require later confirmation.
Try saying
These are phrases to try, with the details to check. They are illustrations, not records of verified deliveries.
“Run shortcut Save idea”
Review the chosen shortcut name. The named shortcut must exist in Apple Shortcuts.
“Run shortcut Save idea with the text try the green version”
Check the prepared shortcut name and input text before starting the handoff.
Details you can send
What is passed to your shortcut
- The execution path selects the named action when available, otherwise the configured default shortcut name.
- The inspected ShortcutManager sends non-empty input as plain text through the Shortcuts app link.
- The supplied registry has no field or attachment matrix for this path. JSON input, file transfer and arbitrary structured parameters are not established by this evidence.
- Match the shortcut’s name exactly, and test it with sample text in Shortcuts before relying on a capture.
- The export does not establish a plan requirement or general structured-field support for this path. Do not infer these from other integrations.
Attachments
The inspected execution path passes text. It does not establish file or recording transfer to Shortcuts.
If something goes wrong
The shortcut name is missing
Set the default shortcut name in Afterthought Settings or choose a named shortcut action.
Shortcuts opened but the workflow did not finish
Open the shortcut directly and check its own permissions, input handling and action results.
The input was not received
Make sure the shortcut uses its text input. The current path sends plain text, not a guaranteed JSON object.
For capture modes, review and Watch setup, read the user manual. If delivery still fails, contact support with the destination, selected route and error message. Leave out account tokens and private content.
About this guide’s source
Based on the app data exported on 9 November 2026 from a local source snapshot labelled 2.7.4. This is not a statement that this version has been released. Options can differ in your installed app.
Capability declarations and inspected runtime code informed this guide. They are not live delivery tests. Where setup or behaviour is not established, the guide says so.
Afterthought is an independent app. Third-party apps and services are provided by their respective owners.