Open-source agentic AI Search Execution Platform. Track AI visibility, find opportunities, and let agents turn signals into prioritized actions and drafted fixes across ChatGPT, Claude, Gemini, Google AI Overviews, Google AI Mode, Perplexity, Grok, and Microsoft Copilot.
TypeScript aeoai-agentai-searchanswer-engine-optimizationbrand-monitoringchatgptclaudecopilotdockergeminigeogoogle-ai-overviewsgrokmcpnextjsopen-sourceperplexityseosupabasetypescript
docs(content): document sending pages to Webflow and choosing where they go (Send to CMS #1331, phase 2 part 5) (#1507)
Cihanfc64c8e0059f
diff --git a/docs/api-reference/webhooks.mdx b/docs/api-reference/webhooks.mdxindex 3a577556a..868d0c191 100644--- a/docs/api-reference/webhooks.mdx+++ b/docs/api-reference/webhooks.mdx@@ -20,7 +20,7 @@ Choose the events a webhook should receive in **Content → Configure Webhook**.| `opportunity.sent` | A user sends a content opportunity to the workflow — from the opportunity page, or several at once from the opportunities list || `daily_pulse.created` | A brand's Daily Pulse is generated (on cloud and self-host alike) || `action_task.sent` | A user sends an Action Center task to the configured webhook |-| `content_draft.sent` | An admin or manager sends a Content Editor page to the CMS: from the editor, a Library row, or up to 25 selected Library pages ([Send to CMS](/guides/send-to-cms)) |+| `content_draft.sent` | An admin or manager sends a Content Editor page to the CMS through the webhook: from the editor, a Library row, or up to 25 selected Library pages ([Send to CMS](/guides/send-to-cms)). Pages sent to Webflow don't fire it || `webhook.test` | **Test Webhook** is pressed in the webhook settings (always sent, independent of subscriptions) |## Verifying requestsdiff --git a/docs/guides/content-editor.mdx b/docs/guides/content-editor.mdxindex cdca09cdc..b888f4deb 100644--- a/docs/guides/content-editor.mdx+++ b/docs/guides/content-editor.mdx@@ -155,7 +155,7 @@ The Content Agent never changes these passages. If you edit one, the editor asks- **Copy HTML** copies the whole page as HTML, HTML blocks and schema included, to paste into your CMS.- **Export** downloads the page as **Word**, **HTML** or **Markdown**. Only the HTML file carries the schema (JSON-LD).- **Add HTML** in the toolbar adds an HTML block: an embed, a widget or a form, kept exactly as written. Ansvisor never runs it. **Edit as HTML** shows the page's source; scripts, iframes and inline styles are removed when you switch back.-- **Send to CMS** (admins and managers) sends the page to your workflow tool through the brand's webhook, for it to create the post in your CMS. See [Send to CMS](/guides/send-to-cms).+- **Send to CMS** (admins and managers) sends the page to the brand's Webflow collection as a draft item, or to your workflow tool through the brand's webhook, for it to create the post in your CMS. See [Send to CMS](/guides/send-to-cms).- **Mark ready** saves the page, sets it to **Ready** and keeps a version in History. If the draft was sent to the Action Center, it also completes its task there. Ansvisor doesn't publish the page: copy or export it to your site, or send it to your CMS.- **Mark published** (the Library's **Status** menu, or the header's **Next step** once the page is ready, when Quality is on): once the page is live, tell Ansvisor where. It asks for the live address, starting from the page it optimizes or your site with the page's slug, and the **Live page** tab measures that address from then. If the draft came from the Action Center, its Publish task is completed once all the action's work is live. On a published page, the header's **Published** button changes the address. A page your CMS reports live, or one published in Webflow, gets its address on its own. An archived page is restored first.- Click **Ready** in the header to move the page back to **In review**. A task that Mark ready completed is open again (**In Progress**), unless someone changed it in the Action Center since or the action is closed.diff --git a/docs/guides/send-to-cms.mdx b/docs/guides/send-to-cms.mdxindex 1d92deb27..9c0b7728a 100644--- a/docs/guides/send-to-cms.mdx+++ b/docs/guides/send-to-cms.mdx@@ -1,13 +1,38 @@---title: "Send to CMS"-description: "Send Content Editor pages to your CMS through your workflow tool, and see where they went live."+description: "Send Content Editor pages to Webflow as draft items, or to your CMS through your workflow tool, and see where they went."----**Send to CMS** sends a Content Editor page to your brand's webhook as a content package: the page ready to publish, its title, slug, meta title, meta description, author and featured image. Your workflow tool (n8n, Make, Zapier or your own endpoint) turns it into a post or page in your CMS. Ansvisor never publishes on its own: your workflow decides whether the page lands as a draft or goes live.+**Send to CMS** sends a Content Editor page to your CMS in one of two ways:-When your workflow tells Ansvisor where the page went live, the draft becomes **Published** and its address shows in the Library.+- **Webflow:** the page goes straight into a collection of your brand's Webflow site as a **draft item**. You publish it in Webflow.+- **Your workflow:** the page goes to your brand's webhook as a content package (the page ready to publish, its title, slug, meta title, meta description, author and featured image). Your workflow tool (n8n, Make, Zapier or your own endpoint) turns it into a post or page in your CMS, and decides whether it lands as a draft or goes live.-## Before you start+Ansvisor never publishes on its own. When your workflow tells Ansvisor where the page went live, or once you publish the item in Webflow, the draft becomes **Published** and its address shows in the Library.++## Connect Webflow++1. In Webflow, open your site's **Site settings → Apps & integrations → API access** and generate an **API token** with **Sites: Read** and **CMS: Read and write**.+2. In Ansvisor, open **Settings → Integrations** with the brand selected, and paste the token in the **Webflow** card. It's checked with Webflow and kept by our connector service. It's never shown again, and Ansvisor's database doesn't hold it. Only **admins and managers** can connect Webflow, pick the collection, replace the token or disconnect; members see where the brand's pages go.+3. Pick the **collection** your pages go to (your blog's, for example), then which of its fields takes what:++ | Part of the page | Webflow field type | |+ |---|---|---|+ | Page content | Rich text | Required |+ | Meta title | Plain text | Optional |+ | Meta description | Plain text | Optional |+ | JSON-LD (structured data) | Plain text | Optional |++ The page's title and slug always go to the item's **Name** and **Slug**. Ansvisor suggests fields from their names (`post-body`, `post-summary`, `seo-title`…); change them if they're wrong, and **Save**. A collection that requires a field Ansvisor doesn't fill can't be saved: **Save** names the field. Make it optional in Webflow first.+4. To use the JSON-LD field, add an **Embed** to the collection template that puts the field inside a `<script type="application/ld+json">` tag.++A site token is one site's, so each brand connects its own. **Replace token** changes it (the collection and fields stay when it's the same site), and **Disconnect** removes it. If Webflow refuses the saved token, the card says so and asks for a new one.++<Note>+**Self-hosting:** Webflow goes through Composio. Set `COMPOSIO_API_KEY` and `COMPOSIO_WEBFLOW_AUTH_CONFIG_ID` (a Composio auth config of the Webflow toolkit with API-key auth) on the API server. Without them, the card says Webflow isn't set up, and pages go to your workflow only.+</Note>++## Set up your workflow1. Open **Content → Opportunities → Webhook Settings**.2. Enter your workflow's webhook URL.@@ -17,6 +42,10 @@ When your workflow tells Ansvisor where the page went live, the draft becomes **Only **admins and managers** can send pages.+## Choose where pages go++Once the brand's Webflow collection is ready, the Send dialog offers **Webflow** (first) or **Your workflow**. Your choice, and where you last sent, is remembered for the brand in your browser. If Webflow is connected but not ready (its token refused, or no collection picked), it shows but can't be picked, with what to fix, so a page doesn't go to your workflow unnoticed. If the dialog can't check Webflow just then, the page goes to your workflow; if you chose Webflow before, the dialog says so, with **Try again**.+## Send one page- **From the editor:** click the paper-plane icon in the header. If **Before you publish** opens first, check it and click **Continue to send**.@@ -32,6 +61,16 @@ The dialog fills the fields from the page, and you can change them before sendinThe slug and meta you send are kept on the draft, so the next send starts from them.+**To Webflow**, the page becomes a draft item in the collection. Sending it again **updates** the same item (a new one is made if it was deleted in Webflow, or after you switch collections); a live item's changes wait for your next publish in Webflow. The item's slug is the page's slug in the form Webflow takes: lowercase letters, digits, `-` and `_`, with accents dropped and dots turned into `-`, so the live address can differ slightly from the slug in the dialog. Webflow's rich text has no tables and Ansvisor doesn't upload images yet, so:++- a table goes as a list, one item a row ("Header: cell · …");+- images aren't sent: add them in Webflow;+- a meta description left empty goes as the page's opening words.++The toast says whether the item was made or updated, and what changed on the way.++Once you publish it in Webflow, the page becomes **Published** at its address on your site: `/{collection}/{slug}` on the custom domain the site was last published to, or on its `webflow.io` address when it has none. Ansvisor checks when you open the Library and once a day, for sends from the last 60 days. A page published in Webflow later than that stays "In Webflow as a draft item"; sending it again starts the check over. A page sent again stays sent until Webflow publishes it again, and a page whose item you deleted in Webflow reads "Removed in Webflow"; send it again to make a new item.+The page goes as **Export** makes it: the HTML without its H1 (your CMS's title field carries it), with the byline line if your brand adds the byline to its content. Ansvisor holds the send while:- a placeholder such as `[figure, source]` is still open (**Fill now** goes to it);@@ -44,7 +83,7 @@ In the **Library**, tick the rows to send (up to 25 at once) and click **Send toThe pages are sent one after another in the background, with a short pause between them so your CMS isn't flooded. The dialog follows them and says how many went, and you can close it at any time: the Library keeps following them. Very long pages go in more than one request, each once the one before has gone; closing the dialog while one waits stops the rest, and it says how many didn't go.-A workspace can send **200 pages in 24 hours**.+A workspace can send **200 pages in 24 hours**, to Webflow and to your workflow together. A page already on its way to Webflow can't be sent there again until it has gone.## See how a send went@@ -53,7 +92,7 @@ Beside each row's status, the Library shows its last send:| Icon | Meaning ||---|---|| Clock | On its way. |-| Paper plane | Your workflow took it (it answered with a 2xx status). |+| Paper plane | Your workflow took it (it answered with a 2xx status), or it's a draft item in Webflow. || Red warning | It failed. Hover it to see what your workflow answered or reported, or why it couldn't be reached. || Blue link | Published. Click it to open the live page. |