xcodesol

mohammadjunaid538

<p>Xcodesol Commerce Workflows provides an admin workflow interface for WooCommerce automation.</p>
<p>Workflow definitions, integration settings, workflow run logs, and subscription status are stored in custom tables in the local WordPress database.</p>
<h3>External services</h3>
<p>This plugin can connect to third-party services only after the site owner enables external services or configures the relevant integration credentials. Payment credentials, payment records, and transaction records are not stored by this plugin.</p>
<h4>Xcodesol Licensing Service</h4>
<p>This plugin contacts Xcodesol’s licensing server at https://www.xcodesol.com/plugin-checkout/payment.php to perform two tasks:</p>
<ol>
<li>
<p><strong>Subscription status check</strong> — When an administrator opens the plugin settings page, the plugin sends the site URL to the Xcodesol server to verify whether a valid subscription exists for this site.</p>
<ul>
<li>Data sent: site URL (home_url()), plugin slug.</li>
<li>When: each time an administrator loads the plugin settings page.</li>
</ul>
</li>
<li>
<p><strong>Remote configuration fetch</strong> — On plugin load, the plugin fetches a remote configuration object (containing the Stripe price ID and other non-secret settings) from the Xcodesol server using a shared plugin token. No personally-identifiable or user-generated data is transmitted in this request.</p>
<ul>
<li>Data sent: a static shared plugin token (no user data).</li>
<li>When: once per hour (result is cached as a WordPress transient).</li>
</ul>
</li>
</ol>
<p>This service is provided by Xcodesol (https://www.xcodesol.com).<br />
Terms of use: https://www.xcodesol.com/plugins/xcodesol-commerce-workflows#terms<br />
Privacy policy: https://www.xcodesol.com/plugins/xcodesol-commerce-workflows#privacy</p>
<h4>Stripe</h4>
<p>Stripe is used to create and verify subscription checkout sessions when an administrator starts or verifies a checkout from the plugin interface. The plugin sends checkout metadata such as store URL, owner email, selected price, checkout session ID, customer ID, and subscription ID.</p>
<p>Service provider: Stripe, Inc. Terms: https://stripe.com/legal Privacy: https://stripe.com/privacy</p>
<h4>Google Sheets and Google APIs</h4>
<p>Google Sheets is used only when an administrator configures a Google Sheets workflow action. Rows can include workflow name, event ID, order ID, product ID, customer email, status, order total, and event payload.</p>
<p>Service provider: Google LLC. Terms: https://policies.google.com/terms Privacy: https://policies.google.com/privacy</p>
<h4>Mailchimp</h4>
<p>Mailchimp is used only when an administrator configures a Mailchimp workflow action. The plugin can send subscriber email address, first name, last name, audience ID, and subscription status to the configured Mailchimp audience.</p>
<p>Service provider: The Rocket Science Group LLC d/b/a Mailchimp. Terms: https://mailchimp.com/legal/terms/ Privacy: https://mailchimp.com/legal/privacy/</p>
<h4>Twilio</h4>
<p>Twilio is used only when an administrator configures an SMS workflow action. The plugin can send the configured sender number, recipient phone number, and message body to Twilio to send SMS messages.</p>
<p>Service provider: Twilio Inc. Terms: https://www.twilio.com/en-us/legal/tos Privacy: https://www.twilio.com/en-us/legal/privacy</p>
<h4>Slack and custom webhooks</h4>
<p>Slack incoming webhooks and custom webhooks are used only when an administrator configures those workflow actions. The destination service depends on the URL configured by the site owner.</p>
<p>Slack terms: https://slack.com/terms-of-service Privacy: https://slack.com/trust/privacy/privacy-policy</p>
<h3>Source code and build tools</h3>
<p>The human-readable React, TypeScript, Tailwind CSS, and Vite source used to build the compiled files in <code>assets/app/assets/</code> is included in this plugin package under the <code>source/</code> directory.</p>
<p>To rebuild the admin app assets:</p>
<ol>
<li><code>cd source/</code></li>
<li>Install Node.js 18+ and pnpm (<code>npm install -g pnpm</code>).</li>
<li>Install dependencies: <code>pnpm install</code> (or <code>npm install</code>).</li>
<li>Build: <code>pnpm run build</code> (or <code>npm run build</code>).</li>
<li>Copy the generated files from <code>dist/</code> into the plugin’s <code>assets/app/</code> directory.</li>
</ol>
<p>Third-party JavaScript libraries bundled in <code>assets/app/assets/</code>:<br />
– React (https://github.com/facebook/react) — MIT licence<br />
– React Router (https://github.com/remix-run/react-router) — MIT licence<br />
– Radix UI primitives (https://github.com/radix-ui/primitives) — MIT licence<br />
– Lucide React icons (https://github.com/lucide-icons/lucide) — ISC licence<br />
– TailwindCSS (https://github.com/tailwindlabs/tailwindcss) — MIT licence</p>


Xcodesol Commerce Workflows

Automate WooCommerce events with workflow triggers, conditions, and actions.

Summix

<p>Sequensy lets you automate repetitive tasks on your WordPress site by building visual workflows. When something happens (a trigger), Sequensy runs a series of actions — creating posts, updating orders, syncing subscribers to your email platform, and more.</p>
<h4>Build Workflows Visually</h4>
<p>Design automation workflows on a visual canvas. Connect a trigger to one or more actions, configure each step with a simple form, and publish. No code, no cron jobs to manage, no third-party automation platform required — everything runs inside WordPress.</p>
<h4>WordPress Triggers</h4>
<p>Start workflows when key events happen on your site:</p>
<ul>
<li><strong>Post Published</strong> — fires when any post type is published</li>
<li><strong>User Registration</strong> — fires when a new user account is created</li>
<li><strong>User Profile Updated</strong> — fires when a user’s profile information changes</li>
<li><strong>Comment Submitted</strong> — fires when a new comment is posted</li>
</ul>
<h4>WooCommerce Triggers</h4>
<p>Automate your store with triggers for order events:</p>
<ul>
<li><strong>New Order</strong> — fires when a customer places an order</li>
<li><strong>Order Completed</strong> — fires when an order is marked complete</li>
</ul>
<h4>WordPress Actions</h4>
<p>Perform tasks on your site automatically:</p>
<ul>
<li><strong>Create Post</strong> — create a new post, page, or custom post type</li>
<li><strong>Update Post</strong> — update the title, content, or status of an existing post</li>
<li><strong>Create User</strong> — register a new WordPress user account</li>
</ul>
<h4>WooCommerce Actions</h4>
<p>Manage your store without manual work:</p>
<ul>
<li><strong>Update Order Status</strong> — change an order to processing, completed, on-hold, etc.</li>
<li><strong>Add Order Note</strong> — append a note to an order (customer-visible or internal)</li>
<li><strong>Create Coupon</strong> — generate a coupon code with a specified discount type and amount</li>
</ul>
<h4>Third-Party Integrations</h4>
<p>Connect workflows to external services you already use:</p>
<ul>
<li><strong>Kit (ConvertKit)</strong> — create subscribers, add tags, and remove tags to manage your email audience</li>
<li><strong>Notion</strong> — create database entries to log data from your WordPress site</li>
<li><strong>Campaign Monitor</strong> — add, update, and remove subscribers from your mailing lists</li>
</ul>
<h4>Features</h4>
<ul>
<li><strong>Visual Workflow Builder</strong> — point-and-click canvas with a clear trigger <span aria-hidden="true" class="wp-exclude-emoji">→</span> action flow</li>
<li><strong>Conditional Filters</strong> — run actions only when specific conditions are met (e.g., post type is “product”, user role is “subscriber”)</li>
<li><strong>Variable Substitution</strong> — pass data between steps using <code>{{Trigger.field}}</code> and <code>{{action_id.field}}</code> syntax</li>
<li><strong>Activity Log</strong> — see a timeline of every workflow execution with status, duration, and error details</li>
<li><strong>Async Execution</strong> — workflows run in the background via Action Scheduler so your site stays fast</li>
<li><strong>Modular Packages</strong> — each integration is a self-contained package you can activate or deactivate independently</li>
</ul>
<h4>External Services</h4>
<p>Sequensy can connect to third-party services to extend your workflow automation capabilities. <strong>Data is only sent to these services when you explicitly connect your account AND create a workflow that uses the service.</strong> You have complete control over what data is sent and when.</p>
<p>No data is sent to Sequensy or Summix servers. All workflow data is stored locally in your WordPress database.</p>
<p><strong>Kit (ConvertKit)</strong></p>
<p>Email marketing platform for creators. Sequensy uses the Kit API to create subscribers and manage tags on your Kit account.</p>
<p>What Data Is Sent: Email address, first name, and any custom fields you configure in your workflow actions.<br />
When Data Is Sent: Only when a workflow executes a Kit action (create subscriber, add tag, remove tag).</p>
<p><a href="https://kit.com/terms" rel="nofollow ugc">Terms of Service</a><br />
<a href="https://kit.com/privacy" rel="nofollow ugc">Privacy Policy</a></p>
<p><strong>Campaign Monitor</strong></p>
<p>Email marketing platform for subscriber management. Sequensy uses the Campaign Monitor API to add, update, and remove subscribers on your lists.</p>
<p>What Data Is Sent: Email address, name, mobile number, custom fields, and consent to track preferences you configure in your workflow actions.<br />
When Data Is Sent: Only when a workflow executes a Campaign Monitor action (add subscriber, update subscriber, remove subscriber).</p>
<p><a href="https://www.campaignmonitor.com/policies/#terms" rel="nofollow ugc">Terms of Service</a><br />
<a href="https://www.campaignmonitor.com/policies/#privacy-policy" rel="nofollow ugc">Privacy Policy</a></p>
<p><strong>Notion</strong></p>
<p>Collaborative workspace and documentation platform. Sequensy uses the Notion API to create entries in your Notion databases.</p>
<p>What Data Is Sent: User-configured properties and content as defined in your workflow actions (can include text, numbers, dates, etc.).<br />
When Data Is Sent: Only when a workflow executes a Notion action (create database entry).</p>
<p><a href="https://www.notion.so/terms" rel="nofollow ugc">Terms of Service</a><br />
<a href="https://www.notion.com/trust/privacy-policy" rel="nofollow ugc">Privacy Policy</a></p>
<h4>Privacy</h4>
<p>Sequensy can connect to third-party services when you configure integrations. For complete details about what data is sent to each service and when, see the “External Services” section above.</p>
<p>No data is sent to Sequensy or Summix servers. All workflow data is stored locally in your WordPress database.</p>
<h3>Development</h3>
<h4>Source Code</h4>
<p>The uncompiled JavaScript/TypeScript source code is included in the <code>admin/src/</code> directory within this plugin.</p>
<p>The admin interface is built with React and TypeScript using Vite. To rebuild from source:</p>
<ol>
<li>Navigate to the <code>admin/</code> directory</li>
<li>Run <code>npm install</code> to install dependencies</li>
<li>Run <code>npm run build</code> to compile assets</li>
</ol>
<h4>Build Tools Used</h4>
<ul>
<li>Vite (build tool)</li>
<li>React 18 (UI framework)</li>
<li>TypeScript (type-safe JavaScript)</li>
<li>Tailwind CSS (styling)</li>
</ul>


Sequensy

Build visual workflows that automate WordPress tasks — connect triggers to actions with zero code.

Xcodesol Commerce Workflows vs Sequensy