KROM AUTOMATION
Krom Automation compatibility with REEID Translate
Krom Automation compatibility with REEID Translate is being evaluated from available plugin evidence. Visual workflow automation engine that connects WordPress events (triggers) to subsequent actions, with execution handled in the background via WordPress Action Scheduler. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Krom Automation.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Krom Automation is documented in the Analytics category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How Krom Automation compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Visual workflow automation engine that connects WordPress events (triggers) to subsequent actions, with execution handled in the background via WordPress Action Scheduler.
- Built-in trigger set covering WordPress user, post, comment, media, and WooCommerce order events (e.g., user registered, post published/updated/deleted, comment submitted/approved, media uploaded, order created/completed).
- Built-in action set including sending emails, creating/updating users and user meta, creating/updating posts and post meta, updating comment status/labels/meta, and making administrator-configured HTTP requests (with JSON response parsing).
- Execution logging and analytics/reporting: per-step execution audit trail (status/output/errors), dashboard metrics (e.g., total executions, active workflows, failed execution count, execution trend), and reports with date filtering and CSV export.
- Conditional branching and delay scheduling within workflows (route based on real data; postpone actions by minutes/hours/days/weeks or custom seconds).
- AI actions (AI generate text, content moderation, auto-tag) that run only when a workflow containing an AI action is triggered and an AI provider is selected; AI providers mentioned are OpenAI, Google Gemini, and Groq.
- Optional external integrations for AI and HTTP request actions: AI actions send configured prompt/workflow data to the selected provider; HTTP Request action sends request URL/method/headers/body and any included workflow data to administrator-configured endpoints.
CONTENT BOUNDARY
Krom Automation capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
Krom Automation and REEID Translate FAQ.
What does Krom Automation do according to the available plugin evidence?
Krom Automation has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for Krom Automation?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Krom Automation?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate Krom Automation in a multilingual WordPress workflow.
REEID documents Krom Automation functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.