HubSpot: Respond.io Action within HubSpot Workflows
under review
Z
Zy
Business Problem:
Currently, there is no native option to trigger respond.io actions (e.g. sending messages) directly from within HubSpot Workflows. This limitation forces teams to rely on external integration platforms or manual steps to initiate conversations or actions in respond.io, complicating their automation ecosystem and increasing the risk of delays or data inconsistencies.
Desired Outcome:
- Native respond.io Workflow Action:Introduce a dedicated respond.io action type in HubSpot Workflows. This allows HubSpot users to seamlessly initiate respond.io actions—such as sending a WhatsApp message, assign the contact and etc.
- Unified Automation Ecosystem:Enable users to maintain a single automated workflow environment, eliminating the need for third-party connectors or manual updates. This ensures consistent data handling, reduces complexity, and streamlines cross-platform communication.
Use Cases:
- Sales Handoffs:When a HubSpot contact reaches a new lifecycle stage (e.g., from Lead to MQL), a HubSpot Workflow could automatically trigger a personalized WhatsApp or SMS message via respond.io. This ensures timely engagement without manually switching tools or exporting contact data.
- Event & Campaign Triggers:Suppose a contact registers for a webinar or completes a form. HubSpot Workflows can immediately prompt respond.io to send a confirmation message or provide next steps, ensuring immediate, automated customer communication.
Current Workaround:
Users must rely on third-party integration tools (like Zapier or Make.com) to trigger the respond.io actions based on HubSpot trigger. This adds complexity, creates additional costs, and is prone to errors or delays.
Ferney Beltrán
The new integration with HubSpot is a big step, but it should be more functional and profound, than seeing the customer's properties in Respond. It is essential to be able to integrate the properties of a customer, with the potential of Respond Workflows: The possibilities are immense and we can alleviate great pain for big customers!
N
Nabilah Binti Salleh
Ferney Beltrán: Hi, thanks for reaching out! We’re already working on new enhancements for the HubSpot integration, and we’d love to hear more about the specific features you’re most looking forward to. Your input is valuable in helping us refine our roadmap.
Feel free to share your use case—it’ll help us prioritize improvements based on user needs.
Looking forward to your thoughts!
Ferney Beltrán
Hello Nabilah Binti Salleh! Here are some examples of how to interact with or bring information from customer properties in HubSpot to Respond:
- Ticket or case status: The customer, in HubSpot, manages the status of reported incidents. By bringing case status information to a Respond Contact Field, it would allow:
- Send template to the client, notifying the client of the status of their case
- That the client self-consult the status of their case.
- Order and order status: The customer, in HubSpot, manages the logistics and fulfillment of their orders. By bringing the status information of an order to a Respond Contact Field, it would allow:
- Send template to the customer, notifying the status of their order, at each of the stages: enlistment, en route and delivery
- Convert HubSpot information into dynamic Respond variables: This can allow:
- Close conversations in Respond and enrich the observation, with relevant information from HubSpot, to avoid unnecessary data crossings.
- Measure the real impact of sales made by Respond, by associating customer closing notes, such as SALES, with the last business number or invoice in HubSpot
For these mentioned cases, the customer can convert the required data as a contact property, to facilitate integration.
S
Shi Hui
under review