Use cases and best practices 

SEO 

This example shows an automation that generates SEO metadata for a new product page.

  1. Trigger: When a Product entry is published.

  2. Constraint: Only run for content type = Product.

  3. Actions:

    • Create related content types (Blog post, Author, SEO metadata).

    • Use AI to generate body text and metadata based on the product entry fields (Name, Description, Unique selling points).

    • Use Patch entry nodes to write the generated content back into the new entries.

  4. Result: The automation creates a complete, SEO-ready blog post linked to the product entry.

Best practices

  • Run automations post-approval: Configure triggers to run only on entries that have passed editorial review to avoid overwriting manual SEO edits.

  • Use clear naming conventions: Label nodes (e.g., Generate SEO Meta Description) to make automations easier to understand at a glance.

  • Review AI outputs periodically: While AI actions accelerate metadata generation, manual checks help ensure accuracy and brand consistency.

  • Keep field mappings clear: Verify that each output field corresponds to the right SEO field (e.g., “metaDescription,” “ogTitle”).

Example

“When an entry of type Blog post is published, generate an SEO meta description using the body text, and update the metaDescription field with the result.”

GIF idea: Show a blog post being published → automation running → AI-generated meta description appearing automatically in the SEO field.

Translation 

This example shows how to automatically translate content when a user finishes a draft, and update the entry. 

  1. Trigger: when workflow step reached (e.g., Ready for translation step).

  2. Condition: run for the content type Product page (or whichever type you choose).

  3. Actions: 

    • AI Action: translate selected fields from a source locale (e.g., English) into a target locale (e.g., German). 

    • Patch Entry: write translated text into the corresponding localized fields.

Optional: App Actions: Notify the team in Slack that translation is complete.

  1. Result: When a content editor moves an entry into the “Ready for translation” workflow step, the automation will:

    • Translate the content automatically using AI. 

    • Update the target locale fields. 

    • Optionally: notify the team through App Actions.  

    • Leave the entry ready for human QA or publishing.