Inbound Webhooks enable seamless CRM integration by allowing external systems to automatically send data using various HTTP request methods like GET, POST, and PUT. This real-time data transfer capability enhances CRM functionality and streamlines workflows, facilitating efficient communication and collaboration across various platforms and tools.

Covered in this Article:

What is an Inbound Webhook?

What are some excellent usage cases for this?

How to use the Inbound Webhook Workflow Trigger?

Step 1

Step 2

Step 3

In your communication Actions:

In If/Else Actions:

Important points to be considered:

What is an Inbound Webhook?

An Inbound Webhook is a robust feature that facilitates the automatic data transfer from external systems to your CRM, improving integration and interoperability. When an event occurs in an external system, an HTTP request (POST, GET, or PUT) is sent to a specific URL linked to a trigger within your CRM, initiating a workflow. This real-time data transfer capability enhances your CRM's functionality and streamlines workflows across various platforms and tools.

By leveraging Inbound Webhooks, businesses can automate processes, reduce manual tasks, and minimize human error, increasing efficiency and productivity. Furthermore, it enables better collaboration between teams, as critical data is readily available and synchronized between different systems. This seamless integration ultimately improves decision-making, customer satisfaction, and business performance.

What are some excellent usage cases for this?

Inbound Webhooks can be used in various scenarios to enhance CRM functionality and automate workflows. Here are a few practical usage cases with examples:

eCommerce Order Integration:

Suppose you have an online store and want to update your CRM with new order information when a customer orders. You can set up an Inbound Webhook in your CRM to receive data from your eCommerce platform whenever a new order is created.

Example: Your eCommerce platform sends an HTTP POST request to the webhook URL with order details such as customer name, email, phone number, and order value. Your CRM then creates or updates the customer's contact information and adds the order details to their record.

Customer Support Ticketing System Integration:

Your company may use a separate support ticketing system to handle customer issues. When a customer creates a support ticket, you can use an Inbound Webhook to send the ticket details to your CRM, ensuring the support team has all the necessary information.

Example: Your support ticketing system sends an HTTP POST request to the webhook URL with the ticket details, including customer email, ticket title, and description. Your CRM then associates the ticket with the corresponding customer record, allowing your support team to access the ticket information directly from the CRM.

Event Registration Integration:

If you host events and use an event registration platform, you can use an Inbound Webhook to send attendee registration information to your CRM.

Example: Your event registration platform sends an HTTP POST request to the webhook URL with attendee information such as name, email, phone number, and event name. Your CRM then creates or updates the attendee's contact information and adds the event registration details to their record, allowing your event team to manage and communicate with attendees effectively.

Lead Capture from Web Forms:

Inbound Webhooks can capture leads from web forms on your website or landing pages and send the data to your CRM.

Example: When a visitor submits a form on your website, your web form sends an HTTP POST request to the webhook URL with the lead's information, such as name, email, and phone number. Your CRM then creates a new lead or updates an existing contact, allowing your sales team to follow up with the lead promptly.

These are just a few examples of how Inbound Webhooks can automate workflows, streamline processes, and enhance CRM functionality in different business scenarios.

How to use the Inbound Webhook Workflow Trigger?

Briefly, bring your data to the system in 3 simple steps using the Inbound Webhook Trigger.

Step 1

Retrieve the webhook URL and use it in your application or system. Next, send the data to the webhook URL using the appropriate HTTP request method (POST, GET, or PUT) and click the "Test Trigger" button.

Step 2

Choose the data received from your application or system using the supported HTTP request method (POST, GET, or PUT) and save it as sample data for future reference. Click on "Load More" to view additional recent data. Once you've selected the desired data, save the trigger.

In this step, you can save the data reference for custom variables, which can be treated similarly to other contact custom fields or Location Custom Variables.

The next step and examples below provide more information on utilizing this reference.

Step 2.1: Send a supported HTTP request (POST, GET, or PUT) to the copied webhook URL and copy the ID in the response.

Step 2.2: Copy the unique ID obtained from the supported HTTP request (POST, GET, or PUT) and use it to search for the relevant mapping reference within your webhook trigger.

Please note that the most recent request will always be at the top of the list.

Step 2.3: Select the correct reference and verify the body.

Step 3

You will be directed to the "Create Update Contact" action after saving the trigger. From there, you can select the necessary fields and map the incoming data you received from the trigger. Please note that to create a new contact or map data to an existing one, you must provide either an email or phone field.

By completing the above steps, you can now use the data you received within the workflow as custom values in email, sms, if/else, etc.

Example:

The custom values of Inbound Webhook can be utilized in all of the actions within your workflow. Some examples of how to do this are provided below.

In your communication Actions:

In If/Else Actions:

As shown above, you can use the values from the Inbound Webhook inside all other actions as you see fit.

Responses:

• When mapping request is Sent
  Status code - 200
  
  

• When you execute actual trigger
  Status code - 200
  
  

Important points to be considered:

• Always send the request using a supported method (POST, GET, or PUT) when interacting with the webhook.
• Ensure the data is sent as a JSON object, the only supported data format.
• To compile correctly, keys must be a single string without space separations; consider using CamelCase or snake_case instead of separating key names with spaces.
• Providing an Email or Phone number in the payload is mandatory, as the workflow requires contact information. An Email or Phone is required to Find or Create the Contact.
• Arrays are not supported in custom values. You can send them in the request but cannot use them inside actions.
• If your data structure changes, re-select the Mapping Reference inside the Inbound Webhook Trigger setup to address those fields in other actions correctly.
• If your Inbound Webhook Trigger URL gets compromised or leaked and you want to prevent unwanted requests, Delete the existing Inbound Webhook Trigger and Add a New Inbound Webhook Trigger. A new URL with a different ending ID will be generated; update your integrations to match the new URL. Once saved, incoming requests from the old URL won't enter your workflow; only requests from the new URL will.

The Custom Webhook - LC Premium Action is a feature enabling real-time data exchange between your CRM and third-party services. It allows tailored requests with various HTTP methods, authorization, headers, and query parameters. This user-friendly tool ensures efficient and accurate workflows while considering API responses and server limitations.

Covered in this Article:

What is the Custom Webhook LC Premium Workflow Action?

Who is this feature useful for?

What are the benefits of this feature?

How to use the Custom Webhook LC Premium Workflow Action?

Fill Url: 

Select a Method

Select Authorization Method

Headers & Query Parameters:

Configure the data to be sent in the Custom Webhook:

Important points to be considered:

What is the Custom Webhook LC Premium Workflow Action?

The Custom Webhook - LC Premium Action is a powerful and flexible feature that enables real-time communication between your CRM system and third-party services. It allows you to configure and send custom data requests to specified URLs using different HTTP and authorization methods. This feature also supports adding headers, query parameters, and mapping custom values to create a tailored request structure that meets your needs. With autocomplete suggestions and user-friendly interfaces, the Custom Webhook streamlines data exchange and ensures accuracy in your workflows. However, it is crucial to consider API response success and server limitations when using this feature to prevent errors and disruptions in workflow execution.

Who is this feature useful for?

This feature is helpful for businesses and individuals who need to integrate their CRM systems with third-party services for seamless data exchange, automation, and enhanced functionality. It is particularly useful for marketers, developers, and IT professionals who want to streamline workflows, improve data consistency, and manage processes more efficiently across various platforms.

What are the benefits of this feature?

The benefits of the Custom Webhook - LC Premium Action feature include the following:

Seamless integration: Enables accessible communication between your CRM system and third-party services, improving data exchange and overall efficiency.

Flexibility: Supports various HTTP methods, authorization methods, headers, and query parameters, allowing you to create custom requests that suit your needs.

Time-saving: The user-friendly interface with autocomplete suggestions simplifies the data mapping and reduces manual effort.

Improved accuracy: Helps ensure data consistency and accuracy across different platforms, reducing errors and inconsistencies.

Real-time updates: Facilitates real-time notifications and updates, enhancing responsiveness and decision-making.

Workflow automation: Streamlines workflows by automating system data exchange, increasing productivity, and reducing manual tasks.

Scalability: Adaptable to various applications and industries, making it a valuable tool for businesses of different sizes and sectors.

How to use the Custom Webhook LC Premium Workflow Action?

Fill Url: 

You have the ability to send data requests to any URL of your choice without the need for coding or server operation.

Select a Method

You can choose any HTTP method that suits your needs, such as POST, GET, DELETE, or PUT.

Select Authorization Method

We support various types of authorization methods, allowing you to choose the one that suits your needs when accessing the webhook. 

Headers & Query Parameters:

In addition to sending a request body, our system allows you to include headers and query parameters when sending requests to a webhook.

Headers can be used to provide additional information about the request, such as authentication credentials, content type, and cache control. 

Query parameters, conversely, can be used to pass parameters to the webhook endpoint, allowing you to filter or modify the response data you receive.

Configure the data to be sent in the Custom Webhook:

The Custom Webhook premium feature allows you to map custom values in any structure that suits your requirements. Our user-friendly textbox provides autocomplete suggestions for all custom values, including inbound webhook variables.

This feature simplifies the mapping process and saves time by suggesting potential values that match your input. Additionally, it helps ensure accuracy and consistency in your data mapping.

Important points to be considered:

• Successful execution of the Custom Webhook Action depends on the successful response of the referenced API. Therefore, if errors are sent back, those will reflect on the Contact's Workflow execution and cause the action to be Failed (and then skipped) or Retry with exponential backoffs. 
• In addition to what was stated above in #1, make sure that the receiving server can handle the number of Executions that you are targeting, or else you might end up with errors due to limits being reached for server issues. The Custom Webhook Action will get fired as soon as the Contact reaches the step, so make sure to add Contacts into the Workflow with the receiving server's limits in mind.

Workflow Slack Premium Action is a feature that enables users to send automated messages to Slack channels and users, streamlining communication and improving team collaboration. The action offers three main events: sending a message to a user, a private channel, or a public channel. 

Covered in this Article:

What is the Slack Notification Premium Action?

What are some excellent Usage cases for this? Who is this useful for?

What are the benefits of this feature?

How to use the Workflow Slack Premium Action?

Send Direct Message to a User

Different Types of User Sources & their use cases

Assigned User (of contact)

Custom Email

Internal User

Slack User

Select a User Source

Message Content

Send a Public Channel message.

Choose a Public Channel

Message Content

Send a Private Channel message.

Choose a Private Channel

Message Content

What is the Slack Notification Premium Action?

Workflow Slack Premium Action is an advanced communication feature designed to automate and streamline messaging within Slack, a widely-used team collaboration tool. This feature allows users to send targeted messages to specific users, private or public channels within their Slack workspace. A user-friendly interface and customizable options ensure effective communication by enabling users to set up and schedule notifications based on their needs.

The action offers three main events:

Sending a message to a user: Users can choose from four options to send a direct message to the right person: Assigned User, Custom Email, Internal User, or Slack User. Each option serves a unique purpose in determining the Message's recipient, ensuring accurate and efficient communication.

Sending a message to a private channel: Users can select a private channel within their workspace to send messages, which will appear as if sent manually by the User who created the Slack integration. This allows for secure communication within a select group of team members.

Sending a message to a public channel: Users can choose a public channel within their workspace to broadcast messages, making information accessible to all workspace members.

What are some excellent Usage cases for this? Who is this useful for?

Workflow Slack Premium Action is helpful for organizations and teams that rely on Slack for communication and collaboration. It helps automate messages and notifications, streamlining the information flow within the workspace. Some good usage cases for this feature include:

• Project Management: Automatically notify team members when new tasks are assigned, project deadlines are approaching, or tasks are marked as complete. This can help ensure everyone stays on track and knows their responsibilities.
• Sales and Marketing: Notify the sales team of new leads, opportunities, or closed deals, allowing them to act quickly and efficiently. Marketing teams can also benefit from automated notifications about campaign performance, content publication, or social media engagement.
• Customer Support: Send automated notifications to the support team when new support tickets are created, escalated, or resolved, ensuring a timely response and efficient issue resolution.
• Human Resources: Notify HR and relevant team members of employee onboarding, training sessions, performance reviews, or policy updates, keeping everyone informed and engaged.
• IT and Development: Send alerts to the IT or development team when new bugs are reported, system outages occur, or software updates are released, allowing them to address issues promptly and maintain system stability.
• Company-wide Announcements: Share important news, updates, or reminders with the entire organization through public channels, ensuring that everyone stays informed and engaged.

What are the benefits of this feature?

Workflow Slack Premium Action offers several benefits to organizations and teams using Slack for communication and collaboration:

• Improved efficiency: By automating messages and notifications, teams can save time and reduce manual effort, allowing them to focus on more critical tasks and improving overall productivity.
• Enhanced communication: This feature ensures that important information is shared with the right people at the right time, reducing communication gaps and misunderstandings within the team.
• Streamlined collaboration: Workflow Slack Premium Action promotes better collaboration by informing team members about project updates, task assignments, and deadlines, helping everyone stay on the same page.
• Increased accountability: Automated notifications for task assignments, updates, or deadlines encourage team members to take responsibility for their work, leading to better overall performance and accountability.
• Customization and flexibility: The feature offers a variety of customization options, allowing users to tailor their messages and notifications to their specific needs, making communication more relevant and effective.
• Real-time updates: Workflow Slack Premium Action enables teams to receive instant notifications about critical events or updates, allowing them to respond quickly and make data-driven decisions.
• Centralized information: By sending messages to specific channels, this feature helps to centralize information within the organization, making it easier for team members to access and reference important updates and data.
• Scalability: Workflow Slack Premium Action can quickly adapt to the changing needs of a growing organization, ensuring that communication remains efficient and streamlined as the team expands.
  
  

How to use the Workflow Slack Premium Action?

The action offers three main events: 

• Sending a message to a user
• Sending a message to a public channel
• Sending a message to a private channel

 Send Direct Message to a User

You will have four options if the event is Send Direct Message to User.

• Assigned User - Assigned User of the Contact
• Custom Email - Add a specific email to search your Slack Workspace for the User and then send out the Message
• Internal User - Users from your account
• Slack User - Directly search your Slack Workspace Users by name.

Different Types of User Sources & their use cases

Assigned User (of contact)

This is used to send out notifications for the assigned User of the contact. In this case, the User's email (in settings>My Staff> User Info) for the User Assigned to the contact is used to find the Slack user.

Custom Email

This is used for all the cases where you need a dynamic user to send notifications to. The custom email that is filled in is used to find the matching of a Slack user.

This is for all those cases where you do not have the User predefined. Either type in the email or select from a list of custom variables using the custom variable picker.  

Internal User

Use this option to send a message to one of the account users. You were typically used to send notifications to particular users responsible for certain sections of your business. Say, sending out information on a successful opportunity won to your finance head. The email of the Internal User selected is used to find the Slack user here.

Slack User

This is as simple as it sounds. Send a direct message to any Slack user of your workspace. 

Please note:

Slack allows only a limited number of users to be fetched simultaneously. So if you don't see your user by typing out the name, please hit the load more button. This will keep searching until you have the required user found. If the user is at the bottom of the list, you might have to hit the load more button several times. This is only for the workspaces having more than 1000 users.

Select a User Source

To start, select one of the four User Sources provided. 

Message Content

Insert Message to send Direct Message to a User. For more formatting options, check here.
You can use the extensive custom variable picker to send information about a contact or any CRM-related information.

Send a Public Channel message.

If the event is Send Public Channel Message, you must select which Public Channel you want to send messages to. 

Choose a Public Channel

Select the desired channel to send the Message.

Please note:

Slack allows only limited number of Public Channels to be fetched at once. So if you don't see the desired channel by typing out the name, please hit the load more button. This will keep searching until you have the required channel found. If the channel is in the bottom of the list you might have to hit the load more button a couple of times. This is only for the workspaces having more than 1000 channels.

Message Content

Insert Message to send to the Public Channel. For more formatting options, check here

You can use the extensive custom variable picker to send out information about a contact or any CRM-related information.

Send a Private Channel message.

If the event is Send Private Channel Message, you must select which Private Channel you want to send messages to. 

Choose a Private Channel

Select the desired channel to send the message.

Please Note:

It's important to be aware that when sending messages to a Private Channel, these messages will be sent as the User who created that Slack Integration, not as the Bot. Therefore, it will appear as if it was sent manually by the User itself.

Slack allows only limited number of Private Channels to be fetched at once. So if you don't see the desired channel by typing out the name, please hit the load more button. This will keep searching until you have the required channel found. If the channel is in the bottom of the list you might have to hit the load more button a couple of times. This is only for the workspaces having more than 1000 channels. 

Message Content

Insert Message to send to the Private Channel. For more formatting options, check here

You can use the extensive custom variable picker to send out information about a contact or any of the CRM related information.

This article explains workflows' "Update Contact Field" and "Clear Field Data" actions. The former allows updating a contact field with a new value, either static or dynamic, while the latter clears the existing value of a custom contact field. Both actions are currently supported for Contact Custom Fields only.

Covered in this Article

What is the Update Contact Field Action in Workflows?

What are some good usage cases for this?

How to use this action?

Select Update/Clear Field Data

Update Field Data

Clear Field Data

What is the Update Contact Field Action in Workflows?

The update contact field action in workflows allows you to update the value of a specific field for a contact. With this action, you can specify a new value for the field, and the contact's existing field value will be replaced with the new value. However, with the new feature, you can also clear the field, i.e., empty the input field or reset it to the default value.

Please Note:

It's important to note that the clear field data feature currently supports only the Contact Custom Fields. 

You can use this action to update or clear multiple fields with static or custom values anywhere in the workflow. The fields can be dynamically updated in workflows wherever they are being used.

What are some good usage cases for this?

Here are some excellent usage cases for the "Update Contact Field" and "Clear Field Data" actions in workflows:

Lead Management: You can use the "Update Contact Field" action to update the lead source field for a contact based on the referral source. This will help you to understand where your leads are coming from and optimize your marketing efforts accordingly. You can also use the "Clear Field Data" action to remove outdated information from your lead records.

Personalization: You can use the "Update Contact Field" action to personalize your email marketing campaigns by updating contact fields such as first or last name. This will help to increase engagement and conversion rates. You can also use the "Clear Field Data" action to remove incorrect or outdated information from contact fields.

Sales Pipeline Management: You can use the "Update Contact Field" action to update the stage of a contact in your sales pipeline based on their progress. This will help you to track and manage your sales pipeline more effectively. You can also use the "Clear Field Data" action to remove contacts from your pipeline if they are no longer a good fit.

Custom Integrations: You can use the "Update Contact Field" action to update custom contact fields based on data from other integrations. For example, you can use Zapier to update a custom field with data from a Google Sheet or form submission on your website. You can also use the "Clear Field Data" action to reset custom fields based on specific triggers or conditions.

How to use this action?

Select Update/Clear Field Data

Update Field Data

Updates the selected field with the provided value. 

The "Update Contact Field" action in workflows allows you to update the value of a specific field for a contact. This feature is useful when updating a contact field with a new value, such as a phone number, email address, or custom field.

To use the "Update Contact Field" action, you must add it to your workflow, select the contact field you want to update and specify the new value you want to set for the field. You can update the field with a static value, a fixed value that you specify in the workflow, or a custom value, which is a value dynamically generated based on other data in your workflow.

For example, if you have a custom field called "Lead Source," you can use the "Update Contact Field" action to update the value of this field for a specific contact. You might want to update the field with a static value like "Website," indicating that the lead came from your website. Alternatively, you might want to update the field with a custom value that is dynamically generated based on the referral source of the lead.

Once the "Update Contact Field" action is executed in the workflow, the contact's existing field value will be replaced with the new value specified in the action. It's important to note that you can use this action to update multiple fields with static or custom values anywhere in the workflow.

Clear Field Data

Resets the selected field to the default value (clears the data). 

Clearing contact fields is a feature that allows you to remove the existing value of a contact field, effectively resetting it to an empty value. This feature is useful when removing a previously entered value from a contact field. When you use the clear field data feature, the contact field value is set to NULL or empty.

Please Note:

It's important to note that the clear field data feature currently supports only the Contact Custom FieldsThis means you can use only clear custom fields you've created for your contacts, not standard fields like first name, last name, or email.

To clear a contact field in a workflow, add the "Update Contact Field" action, select the contact field you want to clear and add a filter for which field you want to clear. Once the workflow is executed, the contact field will be cleared of its previous value and set to an empty value.

It's important to use this feature with care, as clearing a contact field may result in the loss of valuable data. Therefore, it's recommended to use this feature only when necessary and ensure that you have a data backup before clearing any contact field.

The Payment Received trigger is designed to act as a centralized mechanism for capturing all incoming payments across the CRM, including one-time purchases, subscription charges, invoices, and more. It can be customized with filters, such as source type and transaction status, to target specific use cases. This trigger helps businesses automate tasks, streamline processes, and efficiently respond to real-time customer transactions.

Covered in this Article

What is the Payment Received Workflow Trigger, and what does it do?

What are some excellent usage cases for this, along with their benefits?

How to use the Payment Received Trigger?

Workflow Trigger Filters for Payment Received Workflow Trigger

If/Else Conditions for Payment Received Workflow Trigger

Custom Values for Payment Received Workflow Trigger

FAQs

Will this trigger include subsequent subscription payments as well? 

How can I achieve the trigger for successful subsequent subscription transactions?

What does the Customer present/first transaction mean and the Customer not present/subscription transaction?

Will failed payments also be captured in this trigger? 

I have configured the trigger and selected a specific product in the filters. Does this mean that the trigger will fire off when that product is sold anywhere?

What is the sub-source filter?

What is the Payment Received Workflow Trigger, and what does it do?

The Payment Received trigger automates processes and actions based on incoming payments when used in a workflow. It can be configured to respond to specific payment events, such as successful or failed transactions or particular products and payment sources. Here are some detailed functionalities and use cases:

Workflow automation: The trigger initiates the Workflow whenever a payment is received, allowing for automated actions like sending confirmation emails, generating invoices, or updating customer records in a CRM.

Customization with filters: Users can apply various filters to the trigger, such as transaction type, payment source, or product. This enables the creation of targeted workflows for specific scenarios, like subscription renewals, or failed payments.

Real-time response: The trigger operates in real-time, enabling businesses to respond quickly to customer transactions. This can help improve customer satisfaction by providing immediate feedback or resolving issues promptly.

Conditional actions: By using if/else conditions in the Workflow, different actions can be executed depending on the payment characteristics, such as the amount, source, or transaction status.

Reporting and analytics: The trigger can capture payment data for analysis and reporting purposes. By monitoring incoming payments and their attributes, businesses can gain insights into sales performance, customer behavior, and potential areas for improvement.

What are some excellent usage cases for this, along with their benefits?

The Payment Received trigger offers numerous usage cases and benefits, helping businesses automate processes, improve customer experience, and gain insights from payment data. Some common usage cases and their benefits include:

• Automated payment confirmation:
  Usage Case: Send customers automated confirmation emails or messages when Payment is processed.
  Benefits: Enhances customer experience by providing instant payment confirmation, reduces manual tasks, and helps maintain clear communication with customers.
  
  
• Subscription management:
  Usage Case: Automatically update subscription status in the system when a subscription payment is successful or failed.
  Benefits: Ensures accurate and up-to-date subscription information, streamlines subscription management, and reduces manual intervention.
  
  
• Dunning management:
  Usage Case: Automatically trigger dunning email sequences for customers with failed subscription payments.
  Benefits: Improves revenue recovery by addressing payment failures promptly, reduces churn, and enhances customer retention.
  
  
• Customer segmentation:
  Usage Case: Use payment data to create customer segments based on purchasing behavior, such as high-value customers or frequent buyers.
  Benefits: Enables targeted marketing campaigns, helps identify upsell or cross-sell opportunities, and facilitates personalized customer experiences.
  
  
• Payment failure resolution:
  Usage Case: Automatically notify customer support or sales teams to address and assist the Customer when a payment failure occurs.
  Benefits: Enhances customer support, improves customer satisfaction, and helps resolve payment issues quickly.
  
  
• Sales performance tracking:
  Usage Case: Monitor payment data to track sales performance and identify trends, such as best-selling products, seasonal fluctuations, or customer preferences.
  Benefits: Provides valuable insights for strategic decision-making, helps optimize sales strategies, and drives revenue growth.
  
  
• Integration with accounting systems:
  Usage Case: Automatically update accounting records with payment information using outbound webhooks, such as invoicing, revenue recognition, or tax calculations.
  Benefits: Ensures accurate financial reporting, streamlines accounting processes, and reduces manual data entry.
  
  
• Handling trial period transactions: The Payment Received trigger effectively manages transactions involving trial periods for subscription products, such as a 14-day trial. In this example, when a customer signs up for the trial and pays $0 upfront, the trigger categorizes this as a customer present transaction since they are on-session and entering their payment information. After the 14-day trial ends, the customer is charged $100 automatically without entering their payment details again. This subsequent transaction is considered a customer, not present transaction, as it occurs in the background. The Payment Received trigger allows businesses to track and automate workflows around trial period transactions accurately.

  Benefits: By efficiently handling trial period transactions, businesses can enhance customer experience, improve subscription management, and reduce manual intervention, increasing customer satisfaction and retention.

• Integrating Text2Pay links: The Payment Received trigger supports Text2Pay links as a payment source, enabling businesses to automate workflows for payments received through text message-based methods. By incorporating Text2Pay links in the trigger's configuration, businesses can effectively manage and respond to these transactions, improving the overall customer experience and streamlining payment processing.

  Benefits: Utilizing Text2Pay links with the Payment Received trigger allows businesses to reach a wider audience, expedite payment processing, and simplify customer communication, ultimately leading to increased revenue and customer loyalty.

How to use the Payment Received Trigger?

Inside a workflow, add a workflow trigger called Payment Received.

Please Note:

Choosing a filter allows you to choose its respective Sub-filters the next time you add a filter to the same workflow trigger. 

Workflow Trigger Filters 

for Payment Received Workflow Trigger

You can then make your Workflow trigger more specific using filters. Here is a table of all the available filters and sub-filters.

If/Else Conditions for Payment Received Workflow Trigger

Once you have added your desired set of Filters and Sub-Filters to your workflow trigger, you can add an If/Else Condition for Payment if you need to branch out the Workflow based on certain conditions. 

This Table explains the possible If/Else Conditions and their branches.

Custom Values for Payment Received Workflow Trigger

When you use the Payment Received Workflow trigger, you have access to a set of Custom Values that you can populate within SMS, Emails, Internal Notifications, etc. This Table explains the custom values in detail.

FAQs

Will this trigger include subsequent subscription payments as well? 

Yes, the trigger will fire whenever a payment is received from the end customer directly on an order form submission and when the subscription is charged in the background.

How can I achieve the trigger for successful subsequent subscription transactions?

Since the subscriptions can be created in a funnel or website, we can create a trigger for Payment Received and apply the following filters for achieving the use case. The source type is Funnel/Website. The transaction type is "Customer not present/subscription transaction."

The payment status filter can filter successful or failed payments per the use case.

What does the Customer present/first transaction mean and the Customer not present/subscription transaction?

We are categorizing the transaction type into two categories

• Customer present /first transaction - This includes the transactions where the end customer is on-session and making the Payment. This consists of all one-time purchases and the first order placement for a subscription product.
• Customer not present / subscription transaction - This includes the transaction types which run in the background after a subscription has already been created. For example, if a customer purchases a recurring product with a 14-day trial period. The transaction is done while purchasing the recurring product ($0 transaction in this case) would fall into the Customer present/first transaction. After 14 days, when the trial period is over, and you charge $100 for the recurring product, the $100 transaction would fall into the Customer not present/subscription transaction category.

Will failed payments also be captured in this trigger? 

Yes, by default, without any filters, the trigger runs upon successful and failed payment attempts. For specific use cases around success/failed payments only, we can apply the "Transaction status" filter and set it to either success/failed as per the use case.

I have configured the trigger and selected a specific product in the filters. Does this mean that the trigger will fire off when that product is sold anywhere?

If you have configured the trigger and set the filter for a specific product, it will fire off only when that product is sold in funnels/website/invoices. Using the transaction status filter, we can define whether the trigger should work when the purchase is successful or the purchase is a failure.

What is the sub-source filter?

When you select a source like funnels/websites/invoices, they can have sub-sources, like a payment from the funnel can be coming either via a one-step order form, a two-step order form, or an upsell. You can use these sub-source filters to define the Payment's origin.