ZAPIFY
Zapify compatibility with REEID Translate
Zapify compatibility with REEID Translate is being reviewed using official plugin documentation. WordPress hook–based trigger support, including a custom hook trigger that can listen to any `do_action` name from core/theme/other plugins and expose hook-passed values for placeholder use. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What Zapify does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
Zapify is documented in the Other category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How Zapify compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- WordPress hook–based trigger support, including a custom hook trigger that can listen to any `do_action` name from core/theme/other plugins and expose hook-passed values for placeholder use.
- Automation builder that binds triggers to actions and supports placeholders whose values are substituted at runtime.
- Incoming webhook capability to start automations (with signature verification, rate limiting, and per-source key as described).
- Outgoing webhook capability as an action to call arbitrary URLs with configurable headers/body, with SSRF guarding as described.
- Run logging that records what actions were given after placeholder substitution and indicates reasons when actions were skipped; includes a stated retention period on the free plan.
- Ability to enable/disable automations and individual steps (triggers/actions) without deleting configuration, with restoration behavior described when re-enabled.
- Prebuilt integrations for common WordPress/WooCommerce/form/LMS ecosystems (e.g., WooCommerce order status changes/product purchases; Gravity Forms/CF7/WPForms/Fluent Forms submissions; and listed premium integrations such as Slack, Google Sheets, Mailchimp/ActiveCampaign/ConvertKit/FluentCRM, ClickUp, LearnDash, LifterLMS, Tutor LMS, Easy Digital Downloads, Ninja Forms/Formidable Forms, and Buttons).
TRANSLATION BOUNDARY
Zapify capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
Zapify and REEID Translate FAQ.
What does Zapify do?
Zapify has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does Zapify have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from Zapify?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate Zapify in a multilingual WordPress workflow.
REEID documents Zapify functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.