How to Automate Stripe Payment Notifications with Zapier

What if you need more information about the Stripe payment and need to send this info along to a colleague? In this tutorial, we'll build a zap that automatically captures new payments on Stripe and sends out email and Slack notifications.

How to Automate Stripe Payment Notifications with Zapier

When you get paid on Stripe, you typically receive a generic payment email notification. That email usually contains the following basic info:

  • Payment Amount
  • Customer Name
  • Customer Email Address
  • Customer ID
  • Payment ID

But what if you need more information about the payment and need to send this info along to another colleague? That’s exactly what we’ll cover.

In this tutorial, we'll build a zap that captures new payments on Stripe and automatically sends out email and Slack notifications. To implement this, we'll need to do the following:

  • Set up a payment link in Stripe
  • Set up a Stripe payment trigger event in Zapier
  • Add action steps that send out payment notifications (i.e Gmail, Slack)

You can create a new payment link in the payments section of the Stripe dashboard. To do this, click the 'Payment Links' option in the menu and then on the 'New' button on the right side of the dashboard. You'll be brought to the payment link editor, which allows you to configure your payment link.

You first need to add a product to your payment link. If you already have existing products set up in Stripe, you will see them display with pricing data in the product dropdown menu. You can create a new product by clicking on the button in the dropdown that says 'Add new product.'

To create a new product, you must give it a name, product tax category, and price. Adding a product description and image is optional. You must also indicate if the product will be a one-time payment or a recurring charge.

Once you're finished with the configuration, proceed to make a test payment using the payment link.

I was once asked if there's a way to do this in test mode to avoid creating an actual charge. While you can make a payment using a payment link created in test mode, Zapier won't pick up the trigger event because Zapier only supports the production version of Stripe. I recommend refunding the payment but if that's not an option you can use Stripe Webhooks + Zapier Webhooks as the trigger event. There's a good amount of information to share, so I'll be creating a future tutorial on this topic.

Setting Up The Stripe Payment Trigger

The Stripe integration with Zapier offers a number of excellent trigger events. If you're looking to capture subscriptions, invoices, refunds, or new customers, you can easily use any of these trigger events. Because we're dealing with payments, go ahead and select the 'New Payment' event. The zap will trigger when a new payment is completed in Stripe. Once that's done, proceed to test the trigger. In the test response, you should see the payment you just made via the payment link.

The response has a lot of fields and data. You can go ahead and select what's most relevant for your automation, but for this tutorial, we'll be using output data from the following fields:

  • Customer Name [Charge Billing Details Name]
  • Email [Charge Billing Details Email]
  • Amount [Amount]
  • Create Date [Created Formatted]
  • Status [Status]
  • Charge ID [Charge ID]

Formatting The Create Date (Optional)

This is an optional step, but if your automation requires formatting the payment create date, you can use Formatter by Zapier. For the event, select 'Date/Time.'

Next, map the created formatted output date/time value from the trigger step to the input box. Then, select the 'To Format' that works for you. Zapier gives you many format options but we selected MMMM DD YYYY HH:mm:ss.

As you can see above, the created formatted date from Stripe was transformed to the desired format.

Using Gmail To Send The Stripe Payment Notification

Now that you have the output payment data from the Stripe trigger, you can easily add a send email step and include this data in the subject and body of your email. To do this, add Gmail or Outlook and select 'Send Email' as the event. For the 'To' input field, I just added my own email for test purposes.

As you can see above, the email subject "New Payment in Stripe - [Charge Billing Details Name]" communicates the name of the customer associated with the new payment.

The body includes the actual payment details. I included the customer's name, email, payment amount, payment create date, payment status, and charge ID.

To add these fields to the email subject and body, simply map the output values from the 'New Payment in Stripe' trigger event. Since the date of the payment create date was re-formatted, map the output value of step 2 (Formatter by Zapier). Proceed to test the step and check your email.

As you can see above, the 'Send Email' step worked perfectly and the payment output data is reflected in the subject and body of the payment notification email.

Using Slack To Send The Stripe Payment Notification

The process to send the payment notification via a Slack message is very similar to the send email action above. Once you add the Slack app, select 'Send Direct Message' as the event. This will send a direct message to a user or yourself from the Slackbot.

Then you can map the 'New Payment in Stripe' output data to the 'Message Text' field. Proceed to test and then check Slack.

The content of the Slack message contains the Stripe payment data. I've used the Slack direct message action in many zaps and it's never let me down. It's instant and makes things incredibly efficient for team communication. Used in conjunction with email, it's mint.

Payment notifications are just one of the many Stripe features you can automate. You may need to automate communication around subscription cancellations, failed payments, invoice payment failures, disputes, new customers, new subscriptions, refunds, and so on. If you need any of these automations, check out the supported Stripe trigger events to see if there's a way to capture the data object you desire. If you found the event you're looking for, you can use the general framework of this zap to automate the internal communication of your tech stack apps.

Please let me know if you have any questions about this tutorial. If you found this helpful, please consider subscribing to my newsletter.  


What are you trying to automate and why? I'd love to know!

Do you have an idea for a tutorial?  Share it in the comments!

Need help with an automation? Hit me up - hello@joshnocode.com

I write weekly about business process automation hacks. If that's something you're into, join me, and let's automate together.