Documentation

AI Rewrite & Translation

How to configure AI content rewriting, translation services, and Twig templates as pre-publish content transforms.

AI Content Rewriting Business

Automatically rewrite fetched content using an AI provider before publishing. Rewrites or paraphrases fetched content according to your configured prompt; editorial review and source-rights checks are still recommended.

Supported AI Providers:

  • OpenAI — enter your API key and any model name (e.g. gpt-4.1-mini)
  • Anthropic Claude — enter your API key and any model name (e.g. claude-3-5-haiku-latest)
  • Google Gemini — enter your API key and model name
  • Custom Endpoint — enter the endpoint URL and auth value

Model names are free-text fields — enter any model your account has access to. Check each provider’s documentation for current model names.

Setup:

  1. Go to Ingestics → Settings → AI Rewrite (or Settings → Pre-Publish Transform).
  2. Enable AI Rewrite, select your AI provider, and enter the API key (stored AES-encrypted).
  3. Choose the model and set a rewrite prompt (or use the default).
  4. Configure the rewrite scope: which fields to rewrite (title, excerpt, full content, or a combination).
  5. Set character limits: max title chars (40–1000), max excerpt chars (80–8000), max content chars (1000–120,000).
  6. Enable Strict Mode if desired — when on, items that fail the rewrite guardrails are either skipped entirely or saved as force_draft rather than published.
  7. Enable rewriting per provider on the provider settings screen, and click Save Transform Settings. AI rewrite now runs automatically as the first step of the pre-publish pipeline on every fetch.

AI rewriting uses your own API key — costs are billed by the AI provider based on token usage. Ingestics does not mark up or resell AI calls. AI rewrite runs before translation in the pipeline. If both are enabled, content is first rewritten in its original language, then translated to the target language.

Translation Business

Translate ingested content into any language before publishing. Configure translation per provider so different providers can publish to different language audiences from a single source feed.

Supported Translation Services:

  • DeepL
  • Google Translate
  • LibreTranslate (self-hosted)
  • Custom Endpoint
  • OpenAI, Anthropic, Google Gemini — reuse the AI Rewrite credentials; no separate key needed

Setup:

  1. Go to Ingestics → Settings → Translation (or Settings → Pre-Publish Transform).
  2. Enable Translation, select the translation service, and enter the API key (all stored AES-encrypted).
  3. On each provider, set the Target Language (ISO 639-1 code, e.g. fr for French, de for German).
  4. Select which fields to translate: title, excerpt, content.
  5. Click Save Transform Settings. Translation now runs as the second step (after AI rewrite if enabled) of the pre-publish pipeline.

Twig Templates Business

Use the Twig templating engine to fully control how fetched data is assembled into post content. Access any response field, apply filters, loop over arrays, and use conditionals.

Example: {{ item.title | upper }} — {{ item.source }} assembles a custom post title from two API fields with the title uppercased.

  1. On the provider settings, select Twig Template as the content mode.
  2. Write your Twig template in the editor. All response fields are available as {{ item.fieldname }}.
  3. Use the Preview button to render the template against a live API response before saving.