Choose a read adapter for a customer question, a merchant-installed event for a message trigger, or a configured HTTP endpoint for an external action. Each needs its own credentials, field mapping and result checks.
Illustrative conversation. Real replies depend on your configured source, permissions and returned data.
Shopify and WooCommerce provide configured read-only order information. The full Store workspace remains private beta.
Shiprocket and Razorpay have credential-based read adapters, not shipment creation or payment execution tools.
CRM, helpdesk, sheet and calendar labels help configure a bridge; they do not install native synchronization.
Read the supported source and explain the returned state.
Map the phone and event to an appropriate configured message.
Call only a configured endpoint with the correct authorization and verify its response.
The Zoho CRM preset suggests lead-created or deal-won events. Configure the source platform or middleware to send the fields your WhatsApp rule needs: CRM record ID, customer phone and relevant lead fields. The event name in Repli is a suggestion, not a native subscription installed in that provider. Check that your provider account can emit the event and that the phone field is actually present.
For the opposite direction, an enabled outbound HTTP tool or event can send a configured request to an API or middleware endpoint you control. Supply the method, protected credentials, required inputs and response mapping. Test one record first, inspect the destination and handle an error without claiming success. Repli does not establish native Zoho OAuth, bidirectional contact sync or automatic field discovery.
Example: a lead-created event contains the customer phone and record reference. A matching rule attempts your configured WhatsApp response. The customer replies, and your team can review the conversation. If a later tool writes back to Zoho CRM, verify that external result separately from the message send.
The HubSpot preset suggests contact-created, deal-stage or form-submitted events. Configure the source platform or middleware to send the fields your WhatsApp rule needs: contact ID, phone and the agreed form or deal fields. The event name in Repli is a suggestion, not a native subscription installed in that provider. Check that your provider account can emit the event and that the phone field is actually present.
For the opposite direction, an enabled outbound HTTP tool or event can send a configured request to an API or middleware endpoint you control. Supply the method, protected credentials, required inputs and response mapping. Test one record first, inspect the destination and handle an error without claiming success. Repli does not establish automatic conversation history logging or a native HubSpot synchronization connector.
Example: a contact-created, deal-stage event contains the customer phone and record reference. A matching rule attempts your configured WhatsApp response. The customer replies, and your team can review the conversation. If a later tool writes back to HubSpot, verify that external result separately from the message send.
The Freshdesk preset suggests ticket-created or ticket-resolved events. Configure the source platform or middleware to send the fields your WhatsApp rule needs: ticket ID, requester phone and the status intended for the customer. The event name in Repli is a suggestion, not a native subscription installed in that provider. Check that your provider account can emit the event and that the phone field is actually present.
For the opposite direction, an enabled outbound HTTP tool or event can send a configured request to an API or middleware endpoint you control. Supply the method, protected credentials, required inputs and response mapping. Test one record first, inspect the destination and handle an error without claiming success. Repli does not establish a native ticket queue or complete two-way ticket synchronization.
Example: a ticket-created event contains the customer phone and record reference. A matching rule attempts your configured WhatsApp response. The customer replies, and your team can review the conversation. If a later tool writes back to Freshdesk, verify that external result separately from the message send.
The Zendesk preset suggests ticket-created or ticket-updated events. Configure the source platform or middleware to send the fields your WhatsApp rule needs: ticket reference, requester phone and approved update text. The event name in Repli is a suggestion, not a native subscription installed in that provider. Check that your provider account can emit the event and that the phone field is actually present.
For the opposite direction, an enabled outbound HTTP tool or event can send a configured request to an API or middleware endpoint you control. Supply the method, protected credentials, required inputs and response mapping. Test one record first, inspect the destination and handle an error without claiming success. Repli does not establish native Zendesk OAuth, agent identity mapping or automatic two-way history sync.
Example: a ticket-created event contains the customer phone and record reference. A matching rule attempts your configured WhatsApp response. The customer replies, and your team can review the conversation. If a later tool writes back to Zendesk, verify that external result separately from the message send.
The Intercom preset suggests conversation-started or conversation-closed events. Configure the source platform or middleware to send the fields your WhatsApp rule needs: conversation ID, customer phone and the permitted summary. The event name in Repli is a suggestion, not a native subscription installed in that provider. Check that your provider account can emit the event and that the phone field is actually present.
For the opposite direction, an enabled outbound HTTP tool or event can send a configured request to an API or middleware endpoint you control. Supply the method, protected credentials, required inputs and response mapping. Test one record first, inspect the destination and handle an error without claiming success. Repli does not establish an Intercom inbox replacement or automatic conversation migration.
Example: a conversation-started event contains the customer phone and record reference. A matching rule attempts your configured WhatsApp response. The customer replies, and your team can review the conversation. If a later tool writes back to Intercom, verify that external result separately from the message send.
The Google Sheets preset suggests row-added or row-updated events. Configure the source platform or middleware to send the fields your WhatsApp rule needs: row identifier, phone and explicitly selected columns. The event name in Repli is a suggestion, not a native subscription installed in that provider. Check that your provider account can emit the event and that the phone field is actually present.
For the opposite direction, an enabled outbound HTTP tool or event can send a configured request to an API or middleware endpoint you control. Supply the method, protected credentials, required inputs and response mapping. Test one record first, inspect the destination and handle an error without claiming success. Repli does not establish native Google OAuth, a spreadsheet picker or automatic row append and sync.
Example: a row-added event contains the customer phone and record reference. A matching rule attempts your configured WhatsApp response. The customer replies, and your team can review the conversation. If a later tool writes back to Google Sheets, verify that external result separately from the message send.
The Airtable preset suggests record-created or record-updated events. Configure the source platform or middleware to send the fields your WhatsApp rule needs: record ID, phone and mapped field values. The event name in Repli is a suggestion, not a native subscription installed in that provider. Check that your provider account can emit the event and that the phone field is actually present.
For the opposite direction, an enabled outbound HTTP tool or event can send a configured request to an API or middleware endpoint you control. Supply the method, protected credentials, required inputs and response mapping. Test one record first, inspect the destination and handle an error without claiming success. Repli does not establish native Airtable OAuth, a base picker or automatic bidirectional record sync.
Example: a record-created event contains the customer phone and record reference. A matching rule attempts your configured WhatsApp response. The customer replies, and your team can review the conversation. If a later tool writes back to Airtable, verify that external result separately from the message send.
The Calendly preset suggests invitee-created or invitee-cancelled events. Configure the source platform or middleware to send the fields your WhatsApp rule needs: invitee reference, customer phone and actual booking details. The event name in Repli is a suggestion, not a native subscription installed in that provider. Check that your provider account can emit the event and that the phone field is actually present.
For the opposite direction, an enabled outbound HTTP tool or event can send a configured request to an API or middleware endpoint you control. Supply the method, protected credentials, required inputs and response mapping. Test one record first, inspect the destination and handle an error without claiming success. Repli does not establish Calendly availability lookup, booking creation or automatic reminder import.
Sharing your existing Calendly booking link is ordinary message content. Repli appointments use their own configured slots; do not imply that a Calendly invitee event imports external availability or creates a confirmed booking in both systems.
No. Shopify, WooCommerce, Shiprocket and Razorpay have dedicated read adapters. Other provider presets configure external webhook or HTTP bridges.
No. The full Store workspace is an admin-only private beta. WhatsApp CRM data tools are separate.
No. The event must arrive, match a rule and use an eligible sending path. Templates, consent, quotas and provider errors still apply.
In protected integration configuration or your own server-side endpoint, not public page code or message text.
Pricing · All features · How it works · Blog