Send a Markdown note from another tool
You can now save Markdown into MDFILESTORAGE from the places where your writing already begins. If you draft release notes in a desktop editor, collect meeting notes with an automation, or generate Markdown from another writing tool, you can send that content into your private file library without opening the upload screen each time.
Start by opening your app settings and creating a private access key for the tool you want to connect. Give it a name you will recognize later, such as the app, workflow, or personal script that will use it. Store the key somewhere safe when it is shown, because it is meant to be copied once and used only by the tool you trust.
Next, choose where incoming notes should land. You can point a tool at an existing folder when the content belongs with a project, client, or recurring task. If you do not choose a folder, MDFILESTORAGE keeps these incoming files together in an API uploads folder so you can review them before moving them into a permanent home.
Keep automated notes organized
Use clear filenames before sending files from external tools. A name like weekly-retrospective.md is easier to recognize than a temporary export name, and it also helps you spot when a file already exists in the same folder. If a duplicate name would overwrite something important, the upload is stopped so you can decide whether to rename the new note or update the existing one yourself.
Your normal plan limits still apply. Large files, full storage, monthly upload limits, and file count limits are handled the same way as uploads from the app. That keeps external workflows predictable: a connected tool can add Markdown for you, but it does not bypass the rules that protect your workspace.
Review request activity after connecting a tool
After your first connection is running, return to the API settings page to review request activity. The activity view shows recent attempts, successful uploads, rejected files, rate limits, folder choices, filenames, and short messages for issues that need attention.
Use this report as a simple checklist when you connect a new workflow. Send one small Markdown file, confirm it appears in the expected folder, then check the activity list to make sure the result looks right. If something fails, adjust the filename, folder choice, or file size and try again. Once the first note lands cleanly, you can repeat the same pattern for the rest of your writing workflow.