And since you’re likely using a bunch of different tools in your tech stack to deliver a seamless product experience, that means connecting to an ecosystem you’re already familiar with. 🤗
That's what our Appcues <> Zapier integration is all about, but we wanted to make that relationship even more valuable. So, we did! Now with newly added triggers, our integration lets you build even more Zaps to save time and automate manual workflows.
About the Appcues <> Zapier Integration
Our integration with Zapier lets you connect to 5,000+ products to 10X your product experience. Automate repetitive tasks or trigger changes in one platform based on new information in another. That’s simpler, easier product-led growth. 💪
Appcues can be used as either a trigger or action in a Zapier workflow.
Triggers start a workflow—for example, when a new NPS response is submitted, you send the score to a Slack channel.
Actions complete a workflow—for example, updating a user property in Appcues based on the status of a user’s payment method. Then, you can target a prompt in-app to update their payment method.
What’s new in the latest version of the integration?
The refreshed integration is now:
Built with more triggers. As we mentioned, more triggers = more Zaps. We’ve added 10+ new triggers to connect Zapier to even more Appcues offerings. You can now build zaps based on users who start, skip, or interact with Checklists, Pins, and mobile Flows. You can also trigger zaps based on users who enter a segment.
Is easier to use. You no longer have to go find and plug in a Flow ID, now we just present you with a list of Flows for less back-and-forth work. (You can also start connecting using your public API key.)
And the best news? If you’re currently using the integration, you won’t lose any of your existing Zaps. Simply upgrade to the new version to see all of the new triggers and continue on with your work.
The best ways to leverage Appcues and Zapier together ⚡
We get it–when an integration is this powerful, it can overwhelming to get started. Fear not! Here are some of the most popular ways customers use the integration broken down into three parts: the trigger, the action, and the purpose behind the Zap:
1. Get cleaner data by letting it automatically flow from one tool to another
TRIGGER
ACTION
PURPOSE
A user changes their information in an Appcues Flow or survey.
Update the contact information in your CRM (HubSpot, Salesforce, Marketo, or your preferred CRM tool).
Information that’s automatically updated when things change keeps your CRM database cleaner and more trustworthy. Isn’t that always the dream?
A user finishes an Appcues Flow or checklist.
Add that user to a list in your CRM (HubSpot, Salesforce, Marketo, or your preferred CRM tool).
Automatically make lists of engaged users and customers to use for other purposes.
(on the flip side) A user skips an Appcues Flow or checklist.
Add that user to a list in your CRM (HubSpot, Salesforce, Marketo, or the CRM of your choosing).
Track how many users are skipping key in-app experiences and identify who they are to a) follow-up with them in another way and b) see if you can identify trends to make your experiences better.
A user completes a Typeform survey.
Push those reponses into Appcues user properties.
Automatically make your in-app experiences more personalized.
A new contact is added to your CRM.
Update the contact’s user properties in Appcues.
Use properties to personalize your in-app experience
2. Save time and resources by automating your manual and repetitive tasks
TRIGGER
ACTION
PURPOSE
A new prospect or customer completes their onboarding checklist.
Send an email from HubSpot, Customer.io (or your preferred email automation tool).
Connect your in-app and out-of-app communications for a more seamless customer journey.
A users’ payment information fails.
Trigger a Flow in Appcues.
Encourage an immediate remedy to the problem with an in-app call-to-action that is more likely to get seen.
A customer provides an NPS score.
Send an email from HubSpot, Customer.io (or your preferred email automation tool)
Positive or negative–it’s always great to follow-up on feedback in a timely fashion, making it more likely you’ll gain additional insights.
3. Create visibility for your teams, triggering immediate action
TRIGGER
ACTION
PURPOSE
A customer submits a new Appcues NPS score in your product.
Ping a designated Slack channel with the score and submission details.
Create visibility across large teams by letting them see everything that your customers are saying.
A customer interacts with an Appcues Button Pin.
Notify key team members in Slack or Microsoft Teams.
A personal fav at Appcues–notify teams immediately when customers inquire about pricing or gated features while in the product so that teams can reach out when it’s most likely to have an impact.
4. Collect data in the tools you prefer for faster analysis
TRIGGER
ACTION
PURPOSE
A user completes an Appcues survey.
Push survey responses to ProductBoard (or your preferred product roadmap tool).
Create an automatic feedback stream in the tools your product team is already using for roadmapping and planning.
A user completes an Appcues form.
Create a new card on a Trello board
Create an automatic feedback stream in the tools your product team is already using for roadmapping and planning.
A customer provides an NPS score.
Push NPS scores and submission details to Google Sheets or Airtable.
Collect your data in an organized, digestible way in the tools you already use so that it’s easier to manipulate and report on.
A user starts and completes a checklist.
Push NPS scores and submission details to Google Sheets or Airtable.
Collect your data in an organized, digestible way in the tools you already use so that it’s easier to manipulate and report on.
As you can see in this post, the possibilities really are endless. If you can dream it, you can Zap it. Have a creative way you are using the integration? We’d love to hear it!
And since you’re likely using a bunch of different tools in your tech stack to deliver a seamless product experience, that means connecting to an ecosystem you’re already familiar with. 🤗
That's what our Appcues <> Zapier integration is all about, but we wanted to make that relationship even more valuable. So, we did! Now with newly added triggers, our integration lets you build even more Zaps to save time and automate manual workflows.
About the Appcues <> Zapier Integration
Our integration with Zapier lets you connect to 5,000+ products to 10X your product experience. Automate repetitive tasks or trigger changes in one platform based on new information in another. That’s simpler, easier product-led growth. 💪
Appcues can be used as either a trigger or action in a Zapier workflow.
Triggers start a workflow—for example, when a new NPS response is submitted, you send the score to a Slack channel.
Actions complete a workflow—for example, updating a user property in Appcues based on the status of a user’s payment method. Then, you can target a prompt in-app to update their payment method.
What’s new in the latest version of the integration?
The refreshed integration is now:
Built with more triggers. As we mentioned, more triggers = more Zaps. We’ve added 10+ new triggers to connect Zapier to even more Appcues offerings. You can now build zaps based on users who start, skip, or interact with Checklists, Pins, and mobile Flows. You can also trigger zaps based on users who enter a segment.
Is easier to use. You no longer have to go find and plug in a Flow ID, now we just present you with a list of Flows for less back-and-forth work. (You can also start connecting using your public API key.)
And the best news? If you’re currently using the integration, you won’t lose any of your existing Zaps. Simply upgrade to the new version to see all of the new triggers and continue on with your work.
The best ways to leverage Appcues and Zapier together ⚡
We get it–when an integration is this powerful, it can overwhelming to get started. Fear not! Here are some of the most popular ways customers use the integration broken down into three parts: the trigger, the action, and the purpose behind the Zap:
1. Get cleaner data by letting it automatically flow from one tool to another
TRIGGER
ACTION
PURPOSE
A user changes their information in an Appcues Flow or survey.
Update the contact information in your CRM (HubSpot, Salesforce, Marketo, or your preferred CRM tool).
Information that’s automatically updated when things change keeps your CRM database cleaner and more trustworthy. Isn’t that always the dream?
A user finishes an Appcues Flow or checklist.
Add that user to a list in your CRM (HubSpot, Salesforce, Marketo, or your preferred CRM tool).
Automatically make lists of engaged users and customers to use for other purposes.
(on the flip side) A user skips an Appcues Flow or checklist.
Add that user to a list in your CRM (HubSpot, Salesforce, Marketo, or the CRM of your choosing).
Track how many users are skipping key in-app experiences and identify who they are to a) follow-up with them in another way and b) see if you can identify trends to make your experiences better.
A user completes a Typeform survey.
Push those reponses into Appcues user properties.
Automatically make your in-app experiences more personalized.
A new contact is added to your CRM.
Update the contact’s user properties in Appcues.
Use properties to personalize your in-app experience
2. Save time and resources by automating your manual and repetitive tasks
TRIGGER
ACTION
PURPOSE
A new prospect or customer completes their onboarding checklist.
Send an email from HubSpot, Customer.io (or your preferred email automation tool).
Connect your in-app and out-of-app communications for a more seamless customer journey.
A users’ payment information fails.
Trigger a Flow in Appcues.
Encourage an immediate remedy to the problem with an in-app call-to-action that is more likely to get seen.
A customer provides an NPS score.
Send an email from HubSpot, Customer.io (or your preferred email automation tool)
Positive or negative–it’s always great to follow-up on feedback in a timely fashion, making it more likely you’ll gain additional insights.
3. Create visibility for your teams, triggering immediate action
TRIGGER
ACTION
PURPOSE
A customer submits a new Appcues NPS score in your product.
Ping a designated Slack channel with the score and submission details.
Create visibility across large teams by letting them see everything that your customers are saying.
A customer interacts with an Appcues Button Pin.
Notify key team members in Slack or Microsoft Teams.
A personal fav at Appcues–notify teams immediately when customers inquire about pricing or gated features while in the product so that teams can reach out when it’s most likely to have an impact.
4. Collect data in the tools you prefer for faster analysis
TRIGGER
ACTION
PURPOSE
A user completes an Appcues survey.
Push survey responses to ProductBoard (or your preferred product roadmap tool).
Create an automatic feedback stream in the tools your product team is already using for roadmapping and planning.
A user completes an Appcues form.
Create a new card on a Trello board
Create an automatic feedback stream in the tools your product team is already using for roadmapping and planning.
A customer provides an NPS score.
Push NPS scores and submission details to Google Sheets or Airtable.
Collect your data in an organized, digestible way in the tools you already use so that it’s easier to manipulate and report on.
A user starts and completes a checklist.
Push NPS scores and submission details to Google Sheets or Airtable.
Collect your data in an organized, digestible way in the tools you already use so that it’s easier to manipulate and report on.
As you can see in this post, the possibilities really are endless. If you can dream it, you can Zap it. Have a creative way you are using the integration? We’d love to hear it!
And since you’re likely using a bunch of different tools in your tech stack to deliver a seamless product experience, that means connecting to an ecosystem you’re already familiar with. 🤗
That's what our Appcues <> Zapier integration is all about, but we wanted to make that relationship even more valuable. So, we did! Now with newly added triggers, our integration lets you build even more Zaps to save time and automate manual workflows.
About the Appcues <> Zapier Integration
Our integration with Zapier lets you connect to 5,000+ products to 10X your product experience. Automate repetitive tasks or trigger changes in one platform based on new information in another. That’s simpler, easier product-led growth. 💪
Appcues can be used as either a trigger or action in a Zapier workflow.
Triggers start a workflow—for example, when a new NPS response is submitted, you send the score to a Slack channel.
Actions complete a workflow—for example, updating a user property in Appcues based on the status of a user’s payment method. Then, you can target a prompt in-app to update their payment method.
What’s new in the latest version of the integration?
The refreshed integration is now:
Built with more triggers. As we mentioned, more triggers = more Zaps. We’ve added 10+ new triggers to connect Zapier to even more Appcues offerings. You can now build zaps based on users who start, skip, or interact with Checklists, Pins, and mobile Flows. You can also trigger zaps based on users who enter a segment.
Is easier to use. You no longer have to go find and plug in a Flow ID, now we just present you with a list of Flows for less back-and-forth work. (You can also start connecting using your public API key.)
And the best news? If you’re currently using the integration, you won’t lose any of your existing Zaps. Simply upgrade to the new version to see all of the new triggers and continue on with your work.
The best ways to leverage Appcues and Zapier together ⚡
We get it–when an integration is this powerful, it can overwhelming to get started. Fear not! Here are some of the most popular ways customers use the integration broken down into three parts: the trigger, the action, and the purpose behind the Zap:
1. Get cleaner data by letting it automatically flow from one tool to another
TRIGGER
ACTION
PURPOSE
A user changes their information in an Appcues Flow or survey.
Update the contact information in your CRM (HubSpot, Salesforce, Marketo, or your preferred CRM tool).
Information that’s automatically updated when things change keeps your CRM database cleaner and more trustworthy. Isn’t that always the dream?
A user finishes an Appcues Flow or checklist.
Add that user to a list in your CRM (HubSpot, Salesforce, Marketo, or your preferred CRM tool).
Automatically make lists of engaged users and customers to use for other purposes.
(on the flip side) A user skips an Appcues Flow or checklist.
Add that user to a list in your CRM (HubSpot, Salesforce, Marketo, or the CRM of your choosing).
Track how many users are skipping key in-app experiences and identify who they are to a) follow-up with them in another way and b) see if you can identify trends to make your experiences better.
A user completes a Typeform survey.
Push those reponses into Appcues user properties.
Automatically make your in-app experiences more personalized.
A new contact is added to your CRM.
Update the contact’s user properties in Appcues.
Use properties to personalize your in-app experience
2. Save time and resources by automating your manual and repetitive tasks
TRIGGER
ACTION
PURPOSE
A new prospect or customer completes their onboarding checklist.
Send an email from HubSpot, Customer.io (or your preferred email automation tool).
Connect your in-app and out-of-app communications for a more seamless customer journey.
A users’ payment information fails.
Trigger a Flow in Appcues.
Encourage an immediate remedy to the problem with an in-app call-to-action that is more likely to get seen.
A customer provides an NPS score.
Send an email from HubSpot, Customer.io (or your preferred email automation tool)
Positive or negative–it’s always great to follow-up on feedback in a timely fashion, making it more likely you’ll gain additional insights.
3. Create visibility for your teams, triggering immediate action
TRIGGER
ACTION
PURPOSE
A customer submits a new Appcues NPS score in your product.
Ping a designated Slack channel with the score and submission details.
Create visibility across large teams by letting them see everything that your customers are saying.
A customer interacts with an Appcues Button Pin.
Notify key team members in Slack or Microsoft Teams.
A personal fav at Appcues–notify teams immediately when customers inquire about pricing or gated features while in the product so that teams can reach out when it’s most likely to have an impact.
4. Collect data in the tools you prefer for faster analysis
TRIGGER
ACTION
PURPOSE
A user completes an Appcues survey.
Push survey responses to ProductBoard (or your preferred product roadmap tool).
Create an automatic feedback stream in the tools your product team is already using for roadmapping and planning.
A user completes an Appcues form.
Create a new card on a Trello board
Create an automatic feedback stream in the tools your product team is already using for roadmapping and planning.
A customer provides an NPS score.
Push NPS scores and submission details to Google Sheets or Airtable.
Collect your data in an organized, digestible way in the tools you already use so that it’s easier to manipulate and report on.
A user starts and completes a checklist.
Push NPS scores and submission details to Google Sheets or Airtable.
Collect your data in an organized, digestible way in the tools you already use so that it’s easier to manipulate and report on.
As you can see in this post, the possibilities really are endless. If you can dream it, you can Zap it. Have a creative way you are using the integration? We’d love to hear it!
.png)
