Workflows

Use Workflows to turn repeated tasks into reliable operations. This page helps you create the workflow, run it, debug it, and schedule it.

​

Questions this page should answer

1. Which recurring task should become a workflow first?
2. Are runs completing with useful outputs, not just green status?
3. Where should we fix steps, inputs, or schedule to improve reliability?

​

Before you automate

• Start with one repeated task your team already does manually.
• Define the exact output you expect before building.
• Keep version one short and clear.

​

What this page gives you

• A workflow library with reusable cards.
• Fast creation from templates or from scratch.
• A full editor for step logic and sequencing.
• Per-workflow run, execution, and history views.
• Schedule controls for recurring runs.

​

How to read the workflow library

In the top section:

• Each card is one automation.
• The card title and subtitle tell you the business job.
• Last or Never run tells you adoption and recency.
• The three-dot action on cards helps with quick maintenance actions.

Use the table below cards as your global operations feed:

• Status: run health.
• AI credits: cost per run.
• Inputs: confirms run context.
• Started and Duration: speed and timing consistency.

When a run fails, inspect Inputs first, then step output.

​

Create workflow (template or scratch)

Use Create workflow to start from:

• Start from scratch for custom logic.
• Templates for common execution patterns.

Template-first is faster for most teams. Start from scratch only when your flow is unique.

​

Edit workflow (builder)

The editor is where you design and refine execution:

• Left panel: available step types.
• Center canvas: step order and flow.
• Right panel: AI assistant and properties.
• Top actions: run test, save, and chat-guided edits.

Keep steps explicit. Each step should do one clear job.

​

Content image enrichment workflows

Use content enrichment steps when a draft already exists and needs useful inline visuals:

• Enrich content images: search the project’s Product Images library first, then use AI web search when no first-party image strongly matches. It adds the strongest images near the sections they support and saves the result as a new active editor version. It skips webpage screenshots.
• Create content version: save markdown from another step as a new active editor version without overwriting older versions.

Product Images keep their existing Atomic storage URL and do not need a public source-credit line. External images are imported into Atomic storage and include a visible credit to the original source. This works well after Generate article or when refreshing older text-only drafts. Add clear titles, descriptions, tags, and use cases on Product Images so the agent can find the right first-party visual. Keep target image count balanced; weak visual opportunities should be skipped instead of forcing filler images.

​

Human review steps

Use Human review when a workflow should pause for a person to approve a value or choose from generated options. For list reviews, give the output a clear variable name. When the list is an array of JSON objects, choose the preview field reviewers should see in each row. Full JSON remains available in review details. Keep the full selected object as the downstream output unless the next step only needs one nested value.

​

Programmatic page workflows

Programmatic workflow blocks are reusable. You can combine only the steps needed for the job:

• Detect programmatic page clusters: find repeated competitor URL patterns.
• Programmatic market research: combine the description with the current project and brand kit, identify direct competitors and similar projects, inspect how they implement the requested page pattern, and return one typed pageStructure. The structure includes the recommended page type, WDF/IDF terms, source URLs, layout requirements, and observed content-length ranges.
• Extract programmatic page structure: inspect a urls array and return a reusable page generation schema, shared section structure, and full-page screenshot URLs for each analyzed example. Competitor alternative pages include named sections such as hero, trust bar, comparison table, differentiator cards, testimonials, pricing, FAQ, and final CTA.
• Get Webflow collection structure: read fields from an existing Webflow CMS collection.
• Create programmatic collection structure: create or reuse a Webflow CMS collection from an extracted page structure or existing collection structure.
• Generate structured page content: generate one CMS-ready page object from a writing prompt and pageStructure. The step uses any embedded market research, performs page-specific research, validates required CMS fields and content-length ranges, then returns generated_page.
• Publish mapped content: map workflow values into WordPress or Webflow and publish or save drafts. For Webflow, use Map fields to fill fields one by one, or Paste JSON to pass the whole generated_page object.

​

Map WordPress custom fields

When you select a WordPress connection in Publish mapped content, Atomic reads the ACF fields exposed for the selected post or page type. Use Map fields to map workflow variables or fixed values one by one. Use Paste JSON to provide the complete ACF values object from one workflow variable or a pasted JSON object. Standard WordPress fields such as title, content, excerpt, slug, author, categories, and tags remain separate mappings. Author accepts a WordPress user ID or an exact username, slug, or display name. Use Get content from editor before publishing an existing Atomic content item. It returns one canonical field for each saved value: title, fullDescription, metaDescription, focusKeyword, featuredImageUrl, canonicalUrl, slug, content, wordCount, readTimeMinutes, status and score fields, linked record IDs, outline and NLP data, content structure, and timestamps. fullDescription preserves the complete summary; metaDescription is the short SEO version and is limited to 80 characters, ending in ... when it must be shortened. Read time is rounded up at 200 words per minute. The slug comes from the canonical URL path when available and otherwise from the title. If the custom fields do not appear, open the field group in WordPress and enable Show in REST API. Atomic sends the mapped values in the same WordPress publish request as the post or page. Use Programmatic market research when you need to discover what the market expects before creating a collection. Pass the same pageStructure into both Create programmatic collection structure and Generate structured page content. Use Extract programmatic page structure when you already know which URLs should define the pattern. Use Get Webflow collection structure when you already have a Webflow collection and only need more pages for it. Agents can run the same project-aware capability directly with the Programmatic Market Research tool (programmatic_market_research). The workflow step and agent tool share one implementation and return the same market-research structure. For Webflow collections, pageStructure preserves the exact Webflow type for every field. Short scalar copy should stay PlainText. Repeated blocks, formatted lists, tables, embeds, and multi-paragraph content should be RichText so collection creation, generation, and publishing all use the same type. Generate structured page content accepts only prompt and pageStructure. Put the audience, topic, CTA, constraints, and known facts in the prompt. The step fails instead of silently accepting unknown fields, missing required fields, or values outside researched content-length ranges. The Webflow programmatic collection structure template starts with a collection idea and sample-page prompt. It researches the market, creates the matching Webflow collection from the returned typed structure, generates a sample CMS page, and exposes both the research and generated object in the workflow output. Create programmatic collection structure also returns a Webflow wireframe image. Use wireframeImageUrl or wireframeMarkdown to review the intended Collection Page layout, including visible hero/body bindings and SEO metadata fields that should be configured in Webflow page settings instead of placed as text blocks on the canvas. Paste the returned designerExtensionScript into the Atomic Webflow app while the Collection Page is open. The app runs that installer directly, so its heading hierarchy and CMS bindings stay identical to the generated script. When a generated page already matches the Webflow collection fields, select Paste JSON and use {{generateStructuredPageContent.generated_page}}.

​

Workflow run tab (inputs and output)

This is the control panel for a specific workflow:

• Set run inputs (for example, Current Date).
• Confirm brand context before run.
• Click Run workflow to execute.
• Read final output in the right panel.

Use this view when you need a clean rerun with controlled inputs.

​

Execution tab (live step progress)

Execution helps you debug in real time:

• Left side shows each step and status.
• Right side shows details for the selected step.
• Running steps reveal where time is spent.
• Click Cancel run to stop the selected active run without canceling the workflow itself.

Use this tab to find bottlenecks, stalled steps, or weak step prompts.

​

Run progress state

During a live run, watch for:

• Step stuck in running too long.
• Empty or partial step output.
• Unexpected transitions between steps.

If one step repeatedly slows or fails, simplify that step before scaling schedule.

​

Workflow history tab (single workflow)

Use this tab to review reliability over time for one workflow:

• Compare run outcomes.
• Confirm stopped runs show canceled.
• Track AI credit trend.
• Validate cadence against business needs.
• Re-open older runs for QA checks.

This is the best view for per-workflow quality review.

​

Schedule a workflow (command action)

From workflow detail actions, open Schedule workflow and define cadence:

• Daily
• Weekly
• Bi-weekly
• Monthly
• Inactive

Set schedule only after the workflow is stable in manual runs.

​

What to automate first

Start with tasks that are frequent and rules-based:

• Daily or weekly priorities for SEO and content.
• Content refresh candidate detection.
• Alerting for major movement or failures.
• Structured summaries for stakeholders.

Keep one-off strategy prompts in New chat.

​

What to fix first

If runs are unstable, fix in this order:

1. Inputs (wrong or missing context)
2. Step prompt clarity
3. Step order and dependencies
4. Schedule frequency

Most failures come from bad inputs or vague step instructions.

​

Weekly workflow checklist

1. Review failed runs.
2. Check output quality for completed runs.
3. Improve one weak step in the top-used workflow.
4. Remove duplicate workflows and keep one source of truth.
5. Reconfirm schedule only for proven workflows.

​

Keep in mind

• Small reliable workflows beat large fragile workflows.
• Naming matters for discoverability and adoption.
• A successful status does not always mean useful output.
• Schedule is an operations tool, not a quality fix.

​

Where to go next

• Agents: assign the right specialist to each step
• Automations: schedule recurring agent conversations around your workflows
• Tasks: track follow-through after workflow output
• New chat: prototype tasks before turning them into workflows