Skip to content
WaaruDocs

Connect commerce, CRM and booking apps

Prepare store, payment, shipping, CRM and booking connections, select supported resources, and test the actions and events enabled in your Waaru account.

Reviewed

Use Settings > Integrations to connect the account that owns your business records. Setup requirements differ by provider. Confirm that the connection's setup is enabled before depending on it in a live workflow.

Prepare the correct account

ProviderAccount and setup to verifyChecks before activating a workflow
ShopifyAuthorize the intended store through its app installation and account-linking flow.Review granted access, the correct store and the read or optional order-tagging action offered by the catalog.
WooCommerceUse the supported store authorization flow on the intended HTTPS store.Confirm store access and the read actions/events available to the connection.
RazorpayConnect the intended merchant account through the provider authorization flow.Check account environment and permissions before payment-link or financial actions. Use controlled test records.
ShiprocketComplete the install and seller connection shown in the provider setup.Verify the seller, enabled logistics actions and event setup before using an action that changes delivery handling.
Zoho CRMChoose the correct account and its data-centre region.Confirm the permitted CRM records, actions and event connection.
Cal.comConnect the intended booking account and select its event types.Verify the selected event type, timezone, availability and action result before reporting a booking as confirmed.

For each provider, complete its authorization, return to Waaru, and confirm the connected account. Review number access where the page provides that control. If several accounts are connected, explicitly select the one your action should use.

Select Cal.com event types

Open the Cal.com integration and select the connected account. Use Selected event types to discover and select the event type the flow needs. Recheck that selection if the event type or account access changes. A public booking link alone is not a configured workflow connection.

Use an availability read to find eligible slots when the catalog offers it. Confirm creation in the action result and Cal.com record before telling a customer that a booking exists. Add a recovery path for a slot that becomes unavailable.

Connect an external automation platform

Zapier, Make and Pabbly Connect use their own app or connector setup and a Waaru authorization screen. Start from the provider's available Waaru integration, sign in to the intended workspace, and review the requested access before approving it. Publication or provider setup may still be required before an integration is selectable there.

These provider-authorized actions and event subscriptions are separate from a number-bound Developer API key. Do not copy their contact, audience or campaign operations into a Developer API request unless that endpoint reference explicitly supports the operation.

Verify actions and events separately

A connected account does not prove that a particular event is enabled or that a financial action is permitted. Select an event from the Automation trigger catalog, publish and activate the flow, then inspect a permitted test event in run history. Test a read before a write where practical.

Inspect the source system after a write. If the result is uncertain, reconcile it before retrying. Provider outages, revoked access or missing resource bindings require recovery rather than repeated sends.

Next: Configure connected actions, Google accounts and resources, or manage integration recovery.

On this page