Create landing page draft
postfjord_create_pageCreates a draft page. Nothing goes online: publishing needs postfjord_publish_page and the owner's yes. kind bio is the link in bio page (one per workspace, at the workspace's address); kind landing is a page for one offer, class or signup at address/slug, as many as the plan allows (drafts count). The page gets the brand kit's colours on the chosen style. Images must be ids from postfjord_list_media, a form block needs a signup form id from postfjord_list_pages. The answer has the page and the checks that still stop a publish. On a retry after a timeout or error, send the same idempotency_key: the first answer comes back and nothing is made or sent twice. The blocks from top to bottom. A link in bio page is usually: a hero with layout avatar (the business name, a short line and a photo), a links block with the most important links, and a social block. A landing page for one offer: a hero, a text, a list or faq, a button or a form block. A countdown block (date, time, tz, units, button { label, href }, after, afterText, afterButton) counts down to a date, like a launch or the last day to sign up: use only a real date the person gave, and never move a deadline that has passed to a later one. A location block (name is the business name here; street, city, region, postal, country, phone, tz, week, exceptions) shows the address, opening hours with Open now, a Call button and map links: use only hours and an address the user gave you; never invent them. For a class, call or appointment, use a booking block with the booking link; never invent a link. Write real facts only; do not invent prices, dates or quotes. Text in [brackets] stops a publish; a link written words in a text, the hero line or a faq answer is a link, not brackets, and [words]{#rrggbb} gives those words a color (only when the user asks for one). Any block, and any row of a links block, can show only from one time until another (show).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"title": "<title>"
},
"name": "postfjord_create_page"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | bio or landing (default). | |
| slug | No | landing only: the address after the workspace's, lowercase words with hyphens, like free-class. | |
| style | No | The look, minimal when left out. | |
| title | Yes | The page's name, up to 60 characters. Browsers and shared links show it when the page has no hero heading. | |
| blocks | No | The blocks from top to bottom. A link in bio page is usually: a hero with layout avatar (the business name, a short line and a photo), a links block with the most important links, and a social block. A landing page for one offer: a hero, a text, a list or faq, a button or a form block. A countdown block (date, time, tz, units, button { label, href }, after, afterText, afterButton) counts down to a date, like a launch or the last day to sign up: use only a real date the person gave, and never move a deadline that has passed to a later one. A location block (name is the business name here; street, city, region, postal, country, phone, tz, week, exceptions) shows the address, opening hours with Open now, a Call button and map links: use only hours and an address the user gave you; never invent them. For a class, call or appointment, use a booking block with the booking link; never invent a link. Write real facts only; do not invent prices, dates or quotes. Text in [brackets] stops a publish; a link written [words](https://address) in a text, the hero line or a faq answer is a link, not brackets, and [words]{#rrggbb} gives those words a color (only when the user asks for one). Any block, and any row of a links block, can show only from one time until another (show). | |
| motion | No | true: sections fade in as visitors scroll and photos settle into place; false: the page stands still. New pages start with true. People who ask their device for less motion always see a still page. On a live page the change goes live with the next postfjord_publish_page. | |
| liveFrom | No | Landing pages only: when visitors can see the whole page, as a date and time with an offset or a local time in the workspace time zone (timeZone in postfjord_get_page). Before liveFrom the address says the page does not exist; after liveUntil visitors see that it has ended. null removes it. The link in bio page cannot be scheduled as a whole. | |
| seoTitle | No | A title for Google and shared links, up to 70 characters. | |
| useBrand | No | false keeps the style's own colours instead of the brand kit's. | |
| liveUntil | No | Landing pages only: when visitors can see the whole page, as a date and time with an offset or a local time in the workspace time zone (timeZone in postfjord_get_page). Before liveFrom the address says the page does not exist; after liveUntil visitors see that it has ended. null removes it. The link in bio page cannot be scheduled as a whole. | |
| description | No | What Google and shared links show under the title, up to 200 characters. | |
| hideFromSearch | No | Landing pages only: true keeps the page out of Google and other search engines (a robots noindex tag, and it leaves the sitemap), so only people with the link find it. On a live page the change goes live with the next postfjord_publish_page. | |
| idempotency_key | No | Your own id for this one action, for example post-20261006-launch. Make a new one for each new thing; send the same one again only when you retry. Left out, the exact same call within 10 minutes counts as a retry. |