Export

// setup

In Mudlark, Settings › Export › Add Destination... › Obsidian. Then:

1. Vault. Type the exact name of the vault as it appears in Obsidian’s switcher. Leave blank to use the last-opened vault.
2. Folder. Optional path inside the vault, for example Notes/Inbox. Leave blank for the vault root.
3. Pick what an export should do (next section). New Obsidian destinations default to Add to my daily note, which is what most people want.
4. If you want images, open More Options, turn on Include media in export, then click Choose... next to Vault Root and pick your vault folder. Mudlark stores a security-scoped bookmark, so it only asks once. With this set, images are copied into the vault and referenced with relative paths so they render correctly inside Obsidian.

// what an export does

The setup screen asks what Obsidian should do when you press Cmd+E. Three choices:

• Add to my daily note. The default. Appends to the end of today’s daily note, with a blank-line separator between entries. Enter the same path format your Daily Notes plugin uses in Daily note location, for example Daily/YYYY-MM-DD. Tokens supported: YYYY, MM, DD, HH, mm. Anything else passes through literally, so slashes and dashes are fine. The field previews today’s resolved filename below it.
• Create a new note. Makes a fresh note named after this note’s title. A same-titled export overwrites the previous version.
• Advanced URI plugin. Appends to your daily, weekly, or monthly note. Pick the period. Requires the Advanced URI community plugin. With this mode, your Daily Notes plugin’s template is honored on first creation.

// custom callouts

Mudlark’s highlights, questions, and any custom prefixes you’ve set up render as Obsidian callouts. To match Mudlark’s colors and icons, click Copy Callout CSS under More Options. Mudlark generates a stylesheet from your current callout definitions and copies the file URL to the clipboard. Move it into .obsidian/snippets/ in your vault, then enable it under Settings › Appearance › CSS snippets in Obsidian.

// long-note fallback

Notes longer than about 30,000 characters (long notes, lots of inline images) cannot go through Obsidian’s URL scheme, so Mudlark writes the file directly into your vault instead. The first time this happens, Mudlark prompts you with an open panel to grant access to your vault folder. The decision sticks, so future long notes go straight to the file-write path without asking. If you want to revoke that access, the Vault folder access: granted chip under More Options has a Revoke button.

In Add to my daily note mode, a long-note daily export creates the file without going through Obsidian’s daily-note plugin, so its template won’t run. Use Advanced URI mode if the template matters.

// setup

In Mudlark, Settings › Export › Add Destination... › Apple Notes. Then:

1. Click Install Shortcut to open the prebuilt “Mudlark to Apple Notes” shortcut in iCloud Shortcuts. Add it to your Shortcuts library.
2. Optional: enter a target Notes Folder name.
3. Click Send Test Note. Mudlark sends a small test note. The result line turns green for five seconds if the round-trip succeeded, red with the error if not.

// rolling your own shortcut

The shortcut needs four actions, in order: Get Clipboard, Create Note, Quit App (Mudlark, so focus returns to Notes), Stop this Shortcut. Anything else (folder routing, post-processing) you can add. Name it Mudlark to Apple Notes, the name Mudlark invokes.

// what gets sent

The rendered note, restyled for Apple Notes. Tasks become real Notes checklists, with completed items struck through. Headings map to the two heading styles Notes recognizes. Blockquotes become bullet items, and indented bullets become nested lists. Images embed inline. Supported image types: PNG, JPEG, GIF, WebP, HEIC.

The chooser’s Apple Notes card creates only the Shortcut variant. The clipboard variant exists for users who configured it before the Shortcut version was the default. If you’re starting fresh, prefer Apple Notes (Shortcut) above.

// setup

In Mudlark, if you have an existing clipboard-variant destination it lives in the same Settings › Export panel. Configurable fields:

1. Folder. Optional name of an existing Notes folder. Leave blank for the default.
2. Toggle Include images in export. Images embed inline as base64 and may slow large notes. Turning this off keeps exports fast.

// what gets sent

Markdown is converted to a private Apple Notes pasteboard type with native list markers ({check} for tasks, with completed items struck through and grayed), styled headings, code blocks, quotes, native Notes tables, bold and italic, and images embedded as attachment data. Images larger than 2048 px on the longest edge are downscaled, JPEG at 85% quality.

// in notion, set up the integration once

1. Go to notion.so/profile/integrations and click New integration. Pick the workspace and a name (e.g. “Mudlark”).
2. In Capabilities, grant Insert content and Read content. Save.
3. Copy the Internal Integration Secret (it begins with ntn_).
4. Open the Notion page you want exports to land under. Click the ... menu, choose Connections, and search for your integration. Connect it. The integration can only write to pages where it’s connected.

// in mudlark

Settings › Export › Add Destination... › Notion. Then:

1. Paste the secret into Integration Secret. It stores in the Keychain.
2. Paste the page link into Parent Page URL (the full Notion URL, or just the page ID).
3. Click Check Connection. On success, the result reads Connected as <integration name>. On failure, you get the literal error from Notion.
4. Toggle Include images in export to upload images directly to Notion. Video paths are skipped. Supported image types: PNG, JPEG, GIF, WebP, SVG, HEIC, TIFF, BMP.

// what gets sent

Mudlark sends native Notion blocks built from the rendered note structure, not Markdown text:

• Paragraphs, headings (H1, H2, H3), and dividers.
• To-do items with checked state.
• Bulleted and numbered list items.
• Quote blocks, callouts (with emoji icon), code blocks (with language).
• Equation blocks for math.
• Tables (with header row).
• Images as Notion file uploads, inserted in document order alongside text.

// databases and page properties

When the parent is a Notion database, reserved metadata keys fill matching columns:

• priority goes to a status column if one exists, then a select column, then rich text.
• tags go to a multi-select column where available.
• due, when, and deadline go to the first matching date column.
• source goes to a URL column when the value is a URL, rich text otherwise.

If a status or select option name doesn’t exist in your database, Mudlark reports it as a dropped key with the option name, instead of letting Notion fail with a generic API error.

$ image= and $ icon= set the created page’s cover and icon, respectively. The icon accepts a URL (external image), an emoji, or a Notion icon reference.

// common errors

Invalid or expired Notion token. Check your integration settings. The secret is wrong or has been rotated. Generate a new one in Notion and paste it again.

Notion page not found. Make sure the page is shared with your integration. The integration isn’t connected to the parent page yet. Open the page, click ..., choose Connections, and add your integration.

Notion rate limit reached. Try again in a moment. Notion’s API caps requests. Wait a few seconds and retry.

// setup

In Mudlark, Settings › Export › Add Destination... › Bear. Then:

1. Tags. Optional comma-separated list applied to every export, for example work, mudlark. Bear creates the tags if they don’t exist.
2. Turn on Include media in export under More Options if you want images.

// what gets sent

Bear-flavored Markdown: blank lines around headings removed, runs of blank lines collapsed. The URL scheme uses open_note=no so Bear doesn’t steal focus.

With local images in the note, text and images arrive interleaved in document order. Images larger than 3 MB are skipped (Bear’s limit), with a warning. Images referenced by HTTP or HTTPS URL pass through in the text and Bear handles them natively. Under the hood, Mudlark creates the note first, then adds each text and image segment as a separate URL-scheme step, waiting for Bear’s confirmation between steps.

// setup

In Mudlark, Settings › Export › Add Destination... › Ulysses. Then:

1. Group. Optional group name or path, for example Writing/Blog. Leave blank to drop the sheet into Ulysses’ Inbox.
2. Turn on Include media in export under More Options if you want images attached.

// what gets sent

Ulysses-flavored Markdown (heading levels bumped down by one, table-alignment markers stripped). With images, Mudlark sends the full sheet text first via ulysses://x-callback-url/new-sheet, then attaches each image with ulysses://x-callback-url/attach-image calls. Attachments appear in the sheet’s media drawer, not inline. Supported attachment formats: JPG, PNG, GIF, PDF, RAW.

// tags

Tags are sent as Ulysses keywords through the URL scheme and show up as pills on the sheet. If you connect Ulysses with an OAuth token in its setup screen, Mudlark also strips the inline #tag line from the sheet body so the keyword pills don’t duplicate.

// setup

In Mudlark, Settings › Export › Add Destination... › iA Writer. Then:

1. Library Path. Where in iA Writer the note should land, for example /Locations/iCloud or /Locations/Mac/Inbox. Leave blank for the library root.
2. For images, open More Options, turn on Include media in export, and click Choose... next to Library Root. Pick the iA Writer library folder on disk so Mudlark can copy images there and reference them with relative paths.

// limits and quirks

Long notes (above 30,000 characters in the URL) use the same long-note fallback as Obsidian: a one-time library-folder grant prompt, then a direct file write. The file lands at <library>/<library path>/<title>.md with the same filename sanitization as Custom Folder.

If the picked media root doesn’t contain a typed Library Path, the destination flags a config-time warning so you can fix it before triggering an export.

// setup

In Craft, find the destination folder:

1. Right-click the folder you want exports to land in
2. Choose Copy Deeplink

In Mudlark, Settings › Export › Add Destination... › Craft. The setup screen opens with two choices: Text only (this method) and With images (the API method below). Keep Text only, then paste the deeplink into Craft Deeplink. Mudlark parses out the space ID and folder ID and shows them under the field as read-only confirmation. Use Clear Craft deeplink if you need to start over. Switching the choice later keeps any saved credentials.

// what gets sent

Standard Markdown via craftdocs://createdocument, with a quirk: Mudlark keeps pipe (|) and backtick (`) literal in the URL because Craft’s handler fails to percent-decode them. Without that workaround, tables and code blocks would silently fail. Use Craft (API) below if you need images, since this method drops them.

// setup

In Craft, generate the credentials:

1. Open Craft and go to the Imagine tab in the top right
2. Click Add API Connection
3. Set Permission Level to Read & Write
4. Copy the Endpoint URL and API Key from the modal

In Mudlark, Settings › Export › Add Destination... › Craft, then pick With images at the top of the setup screen. Paste the endpoint into API Endpoint URL and the key into API Key (it begins with pdk_). The steps check themselves off as the fields are filled. The key lives in the Keychain, not in plain text.

// what gets sent

Standard Markdown converted to Craft blocks. With images in the note, Mudlark splits the Markdown around each one, creates the document, then alternates insertBlock (text) and uploadFile (image) calls so they interleave in document order. Files larger than 3 MB are skipped. The export starts asynchronously: the toolbar flashes once the request completes, not at click time.

Per-step failures accumulate into a single “document created, but N files failed” partial-success message, so a bad image upload partway through doesn’t abandon the remaining steps.

// setup

In Mudlark, Settings › Export › Add Destination... › Folder. Then:

1. Click Choose... and pick any folder on your Mac.
2. Optionally turn on Include media in export under More Options.

// what gets sent

Standard Markdown saved as .md, named after the note title. The filename is sanitized: characters forbidden by macOS (/, \,:, *, ?,", <, >,|) are replaced with -. Whitespace is trimmed. The result is capped at 200 characters. An empty title falls back to Untitled. A file with the same sanitized name is overwritten.

Mudlark stores a security-scoped bookmark for the folder, so it can keep writing there across launches without re-prompting. Removing the destination drops the bookmark. If the folder moves or its bookmark goes stale, the export fails with a clear “re-pick the folder” message and a button to re-grant access.

No destinations configured. Cmd+E copies the rendered note to the clipboard as Markdown plus styled HTML, so the receiving app picks the richer one.

The toolbar Copy button. Always visible, independent of destinations. The default click copies in your Copy Format preference (set in Settings › Data › Copy Formats): Markdown, Plain Text, Rich Text, Rich Text with Images (RTFD), HTML, Apple Notes, or Mudlark (the raw.mudlark source). Click the dropdown to get an explicit Copy Source action that copies the raw left-pane text exactly as you typed it.

Apple Notes “Robust export” toggle. When the Copy Format is set to Apple Notes, an extra Robust export toggle appears below it. With this on, the clipboard write uses the same private Notes pasteboard format as the Apple Notes (clipboard) destination, with native tables and inline images. The setting is marked experimental: a future macOS update could break it.

Copy Source is bound to Cmd+Shift+C and Copy Rendered to Cmd+Opt+C by default. Both can be rebound in Settings › Shortcuts.

// setup

In Mudlark, Settings › Export › Add Destination... › Todoist. Then:

1. Click Sign in to Todoist. A browser window opens for OAuth sign-in. Approve. The step checks itself off. The OAuth token is stored in the Keychain, scoped to this destination.
2. Project Name. Once you’re signed in, the dropdown lists your Todoist projects. Pick one, or leave Inbox / Default selected to send tasks to your inbox.
3. Toggle Include completed tasks if you want already-checked items to come along (they arrive pre-completed in Todoist).

Click Disconnect in the same setup screen to revoke the token. Multiple Todoist destinations can use different accounts: each has its own OAuth credentials, independently.

// limits and quirks

Mudlark refreshes the OAuth token automatically when it expires, and retries with increasing delays when Todoist rate-limits, so transient API hiccups don’t require re-syncing the destination by hand.

// setup

In Mudlark, Settings › Export › Add Destination... › Things. Then:

1. List Name. Optional name of a Things list (project or area). Leave blank for the inbox.
2. Tags. Optional comma-separated tags applied to every task. Things only applies tags that already exist.
3. Toggle Include completed tasks if you want already-checked items.

No sign-in required. Mudlark uses Things’ things:///json URL scheme, so all tasks arrive in a single round trip with hierarchy intact.

// structure mapping

In Mudlark, a named block becomes a Things to-do, and the items inside that block become its checklist-items, not separate to-dos. This matches Things’ data model (where checklists live inside to-dos, not as their own type). If you want each line to be its own to-do, leave them outside a named block.

// limits

Things’ URL scheme has a length cap around 40 KB. Mudlark logs a warning if a single export gets close. The first time you trigger an export, Things prompts you to enable URL-scheme support. Click Enable. You can change this later in Things at Settings › General › Things URLs.

// setup

In Mudlark, Settings › Export › Add Destination... › Reminders. Then:

1. List Name. A dropdown of your existing Reminders lists. Pick one, or leave Inbox / Default selected for the default list.
2. Toggle Include completed tasks if you want them.

The first time you export, macOS asks for Reminders access. If you decline, you can grant it later under System Settings › Privacy & Security › Reminders.

// structure mapping

Sub-tasks are added as separate top-level reminders in the same list, not nested. Apple’s Reminders database has no sub-task field Mudlark can write to, so flattening is the most accurate representation.

// metadata mapping

Reminders carries the richest set of native fields after Todoist: $ due= sets the due date, $ when= the start date, $ remind= an alarm (absolute or relative offset), $ repeat= a recurrence rule, $ location= a location, $ url= a URL, $ priority= a priority.

By default, Auto-alarm on due date is on: setting $ due= without an explicit $ remind= creates an alarm at the due time so the reminder actually notifies. Turn it off in the destination’s metadata options if you’d rather file silent reminders.