Yektabot

Yektabot connects a WooCommerce store to the external Yektabot service. The service manages end-to-end automated conversational sales workflows on Instagram, Telegram and the Bale messenger. This plugin creates and maintains WooCommerce product webhooks, supports a full product synchronization, and provides a payment return flow for supported payment gateways.

WooCommerce and a Yektabot account are required. The plugin is free software. The external Yektabot service has its own account requirements and may require a paid plan; see https://yektabot.com/prices. Instagram, Telegram and Bale connections are configured in the Yektabot service, not directly in this plugin.

Features:

• Connect a store to an account selected in the Yektabot dashboard.
• Synchronize product.created, product.updated and product.deleted events.
• Send an initial product catalog in batches.
• View connection status and local activity logs in the WordPress dashboard.
• Use an optional payment flow with an existing Zarinpal or Zibal merchant account.
• Disconnect the integration and remove its product webhooks.

The administration interface is currently in Persian. Persian documentation is included in readme-fa.txt; directory translations use translate.wordpress.org after approval.

External services and data

Yektabot

Service: https://yektabot.com/
Account dashboard: https://app.yektabot.com/
Terms of use and privacy policy: https://yektabot.com/terms

The plugin communicates with app.yektabot.com after an administrator explicitly connects the store. Connection starts a browser redirect to the Yektabot dashboard, including the store URL, a return URL and a temporary verification state.

To allow Yektabot to manage store products and orders, the connection creates a WooCommerce REST API key with read/write access and sends its consumer key and consumer secret, the store URL and selected account ID to Yektabot over HTTPS. These credentials grant access to WooCommerce store data, including customer and order information available through the WooCommerce API. Only connect a store you are authorized to manage.

While connected, product webhooks and full synchronization transmit product data, including unpublished products, such as IDs, names, descriptions, SKUs, prices, stock, categories, attributes, variations and image URLs to the configured Yektabot webhook. Synchronization progress and connection checks also communicate with the service. Product events are sent when products are created, updated or deleted; a full synchronization is started by an administrator.

Explicit connection, disconnection and payment-setting actions notify the service of the account ID, connection installation ID, plugin version, store URL, selected account information, available gateway names, payment-enabled status and payment callback URL. These messages keep the service’s checkout configuration in sync with the store. They are authenticated service operations rather than installation analytics.

When the payment integration is enabled and used, the plugin sends the signed payment token, payment result, gateway name, payment reference and related verification metadata to Yektabot so that the service can update the corresponding order. The supported gateways are described below. Merchant credentials are read from the store’s existing gateway settings and used for gateway API requests.

The plugin does not send installation or activation analytics, fetch remote branding assets, or contact a license/author-verification service. Local activity logs are stored in the WordPress database and can be cleared from the plugin page. The site operator is responsible for informing customers about the connected services and their handling of store and payment data.

Zarinpal (optional)

Service: https://www.zarinpal.com/
Terms of use: https://www.zarinpal.com/terms
Privacy policy: https://www.zarinpal.com/policy

If Zarinpal is selected and the payment flow is used, requests are sent to api.zarinpal.com to create and verify a payment, and the customer is redirected to www.zarinpal.com to pay. Request data includes the merchant ID, amount, callback URL, order description and, when provided by the signed payment request, the customer’s mobile number. Verification sends the merchant ID, payment authority and amount. A configured Zarinpal merchant account is required.

Zibal (optional)

Service: https://zibal.ir/
Privacy policy: https://zibal.ir/privacy-policy

If Zibal is selected and the payment flow is used, requests are sent to gateway.zibal.ir to create and verify a payment, and the customer is redirected there to pay. Request data includes the merchant credential, amount and callback URL; verification includes the merchant credential and payment tracking ID. A configured Zibal merchant account is required.