Creating blueprints
A field-by-field guide to the blueprint composer and how to write instructions that work.
Open Blueprints in the app. The quickest way is the box at the top: type what you want in one line, optionally pin an Integration or a Name, and tap Create. Postface works out the name, schedule, category and accounts from your words, saves the blueprint, and opens it so you can check what it decided. Build one field by field opens the full composer instead, and templates and the library fill it in for you.
How a blueprint is created
- Your words. The line you typed is kept exactly as written, alongside the finished instruction.
- Draft. Luna reads your connected accounts and plan, then fills every field. If the AI is paused or busy, a rules-based draft takes over so you are never blocked; the blueprint tells you when that happened.
- Checks. Schedules your plan does not include fall back to daily. Only accounts you have connected are attached; anything else the task needs is listed as a note ("Connect Canvas…") instead of being assumed.
- Saved. The blueprint is stored under your account with how it was created (typed, composer, template or library copy), the plan you were on, and the draft notes. It starts active and private.
- Runs. Each run records the tools used, the outcome and the text sent, visible on the blueprint page.
Storage and who sees what
- Blueprints and their run history belong to one person; nobody else can read them unless you share a blueprint to the library and a reviewer publishes it.
- Plan decides how many you may keep and which schedules you may use (see Blueprints). Creator accounts have the Pro allowance.
- Library copies keep a link to the original, so install counts and later updates can be traced without exposing the author's account.
The composer
| Field | Notes |
|---|---|
| Name | Up to 60 characters. Texting this name runs the blueprint. |
| Instruction | 12 to 2000 characters of plain language. This is the whole brief Postface works from. |
| Integrations | Pick which connected accounts the blueprint may use. Only accounts you have already connected are offered; custom MCP integrations appear here once they are working. |
| Schedule | Daily, weekdays, weekly, hourly (Pro and above) or on demand. Scheduled runs use your local time. |
| Category | Used to organise the library: Work, Engineering, Personal, Health, Content or General. |
Writing a good instruction
- Say what to look at and how far back. "Unread email from the last 12 hours" is better than "my email".
- Say what to report. Name the two or three things you want in the text and the order you want them in.
- Say what to skip. "Ignore newsletters and calendar invites" saves the character budget for what matters.
- Keep texts short. Each plan has a character ceiling per run (see Blueprints). Postface trims to fit, so put the most important item first.
Running and testing
Tap Run on any blueprint to run it immediately, or text its name. Each run is recorded with its outcome: Done (a text was sent), Nothing (Postface found nothing worth reporting and stayed quiet) or Failed with the reason. Pause a blueprint at any time to keep it without running it.
Taking actions
Blueprints that use GitHub, Slack, Notion or Canva can act as well as read: open an issue, post a message, add a note or create a design. Say so explicitly in the instruction. Mail and calendar integrations are read-only.