🚧 Botify Workflows is in open beta as of November 23, 2026. To join, contact your Botify account team.
Overview
A workflow is an orchestration of tasks run by agents, at scale, that you save and run again. Each workflow chains steps together, for example: pull page content, ask an agent to process it, and write the result back. Workflows facilitate the jobs you repeat or run across many pages. You describe the job in plain language to your AI assistant, the assistant builds the workflow, and runs it on your Botify data.
You can:
Build a new workflow from a job description.
Adapt an existing template, such as adding a step to the FAQ generation template.
Run a template as it is.
Examples of custom workflows:
Run the structured data audit with an extra step that pulls Search Console clicks, so the audit covers your top pages by clicks.
Find questions where your brand is missing from AI answers in an AI Visibility campaign, then suggest title and meta description changes for the matching product pages.
Rewrite titles and meta descriptions for a seasonal campaign.
👉 A template is a workflow Botify has already built and validated, ready to run as it is or to adapt to your preferences.
Where you can run workflows
Location | Setup | Building workflows |
Claude, with the Botify MCP plugin | Connecting to the Botify MCP in Claude | The plugin includes the skill that builds workflows; there is nothing else to set up. |
Botify Assist | None | Call the Builder skill in Assist; or create and run workflows in Assist > Workflows. See Managing workflows in Botify. |
Other AI assistants connected to the Botify MCP | Ask the assistant to read the |
In Assist, the model is set by Botify. While you can combine Botify data with the data from Assist’s integrated agents, you cannot add external agents or MCPs.
⚠️ The builder skill is available in Assist and Claude through the plugin. Everywhere else (i.e., Claude without the plugin any other LLM client), the LLM must call the workflows_documentation tool before building a workflow to retrieve the build instructions.
Checking the Botify plugin in Claude
In Claude, go to Settings > Customize, then select the Botify plugin.
Open the Skills tab and check that the
botify-workflowsskill is listed.
💡 Ask Claude for something from your Botify data. If Claude can't access it, the plugin isn't connected.
💡 If you have been accepted into the Workflows beta and don't see the tools in Claude, you may have to refresh your tools list:
When your assistant uses a workflow
Your assistant decides whether a request needs a workflow or a simple task in the conversation. A workflow fits a job that is:
Repeated on a regular schedule, with results you compare from one run to the next.
Made of several steps applied to many items, such as pages or keywords.
To ask for a workflow explicitly, include "Botify workflow" in your request.
How a workflow runs
Your assistant creates a workflow only when it judges that the job needs one. It runs a sample first only when the job needs it and covers many items.
Describe the job in plain language.
Build: The assistant creates the workflow.
Check: Confirm the scope (which pages or items the workflow covers).
Sample: The workflow runs on a small set of items when applicable for the job type. Review the output quality.
Full run: Confirm the run size and credit usage, then start the full run.
Follow: The assistant gives you a link to follow the run in Botify. When the run is done, ask the assistant to continue.
👀 If any of these steps did not process, it may be due to LLM choices that we don’t always control. In this case, you can ask for a specific step.
You will not be notified in the conversation when a run finishes. Ask your assistant for the run status, or open the link.
To check progress, open the run link. The run page shows whether the run is pending, done, or failed.
Managing workflows in Botify
In Botify, go to Assist > Workflows to create, run, and follow workflows. You can view each workflow, its runs, and each node's input and output (the first 10 entries, and all errors). If a run fails, you can see which node failed and why.
A workflow's page shows:
Previous runs: Each run's status (Done or Failed), whether it was a test run, its start and end times, and the user who launched it. Select Go to result for a completed run or See error for a failed one.
Setup: The workflow's settings. They are saved on the workflow and applied to every run.
Workflow nodes: The steps of the workflow and their configuration.
A run's page shows its results. For an FAQ test run, it shows how many answers have no issue and how many mention a sensitive topic, and the Q&A pairs for each sampled URL with their flags (for example, Pricing). You can download the results as a CSV file.
Running a workflow in Botify
There are two methods for running a workflow:
Running a workflow from a template
In Botify, go to Assist > Workflows.
Click a template in the Templates section to create a workflow from it.
Optionally review the workflow’s nodes and logic, clicking each node to view its source.
Click Create a workflow to get started.
Optionally click Edit setup to change the settings and save. You’ll have another opportunity to do this in the next step.
Review the setup, then click Launch Workflow. You can navigate away from this page while the workflow runs.
👉 For some workflow types (e.g., FAQ), this will launch a test run, and you can launch the workflow on the full scope after.
If you left the page while the workflow ran, click Go to result.
If you are satisfied with the result, click Launch full scope to execute the workflow across all pages. Otherwise, edit the setup and try again.
When the run is complete, you can download a report in CSV format.
Running from an existing workflow
Your previously run workflows are at the bottom of the page, with the number of runs for each and the date of their last runs. Runs launched by Botify team members do not appear in your list.
To start from a previously run workflow:
Click the workflow name, then proceed with Step 5 above; or
Click New run to start the run. You will be prompted to review the setup before launching the workflow.
Workflow templates
The following templates are currently available: These are built on your site data collected during Botify crawls:
FAQ generation
This template drafts FAQs from the content of your product detail pages (PDPs).
Runs on up to 16,000 URLs per run.
Uses the same set of pages for the scope check, the sample and the full run.
You can upload a list of URLs by CSV.
Page content comes from the HTML of your crawl data. If your pages render content with JavaScript, ensure your crawl is set up to render JavaScript.
FAQ generation settings
Settings are saved on the workflow and applied to every run.
Setting | Description | Default |
Define which product pages to include | Describe in plain language which product pages to include or exclude, for example: "Take only in-stock shoes priced above €100. Exclude outlet products." Select Count URLs to see how many URLs the description matches. | Not set |
Tone of voice | How the answers are written. | Botify default tone of voice: written from the website owner's point of view, natural and conversational, 1–3 sentences per answer. |
Words to avoid | Words the answers must not use, for example: cheap, discount, amazing. | Not set |
Topics to include or avoid | What the questions should and shouldn't cover. | Not set |
Sensitive topic flags | Flags answers that mention pricing, competitors, medical advice, or legal claims. | On |
Max Q&A pairs per URL | Maximum number of question-and-answer pairs per page. Pages with little content may get fewer. | 3 |
URLs in test run | Number of pages in the test run. | 5 |
Max URLs in full run | Maximum number of pages to include in the workflow’s full run. | 100 |
Push to PageWorkers (draft) | Creates a draft optimization in PageWorkers. | Disabled |
FAQ generation outuput
CSV file: One row per Q&A pair, with the columns
url,question,answer,flag_status,flag_category, andflag_rationale. To open the download link, you must be logged in to Botify with access to the project.PageWorkers: A full run pushes the FAQs to a draft PageWorkers Page Editor optimization named "FAQ for PDPs." Test runs don't push to PageWorkers. The FAQs don't go live until you review the draft and select Deploy to production.
Structured data audit
This template audits the structured data (JSON-LD only) across your site's page types and reports what is missing or malformed. It does not fix structured data or push changes to PageWorkers.
Groups your site segments into page types and samples URLs from each.
For each URL, recommends structured data types, extracts the existing JSON-LD, and optionally retrieves Google URL Inspection data.
Workflow credit consumption
Workflow runs use credits from your organization's credit allowance, like other Botify agents. See Monitoring Agent Credit Consumption.
Each run is capped at 100,000 credits and the remaining credit envelope.
If a run reaches the cap, it stops with an error. You can run it again later.
A run can go slightly over the cap, by up to one step.
Large runs can use a significant share of your allowance. Before a full run, check the run size and expected credit usage with your assistant.
Known limits
There is no notification in the conversation when a run finishes. Ask your assistant for the status, or follow the process directly in the workflow within Botify.
Structured data audit is audit only. It does not push changes to PageWorkers.
FAQ generation runs on PDPs only, up to 16,000 URLs per run.
Outside Claude with the Botify plugin and Assist, the assistant must read the
workflows_documentationtool before building a workflow.Permissions during the beta period do not restrict read-only users from running workflows.
AI-generated output quality can vary. Review the sample before a full run.
If you took part in the Tech Preview
You must still apply to the beta program; you are not automatically enrolled. You keep the outputs you already received in the tech preview. There is nothing to migrate or sign in the beta program. You can now build and run workflows yourself, and your runs use your organization's credits.
Reporting a problem
Contact your Botify account team and include:
The workflow URL and the run that failed.
The step where it failed and the error message.
The pages concerned.
What you asked the assistant and what you tried.
See also:








