A blog about productivity, workflow best practices, company building and how to get things done with less work.


Entries Tagged “PayPal”

Sending email is hard. Just take a look at the success of transactional email services like Mandrill, Sendgrid, and Mailgun.

Every web application under the sun has to send email too so there’s a huge demand for services who can help developers send email more efficiently.

The thing is, if sending email is hard for developers, guess how hard it is for marketers, support teams and sales guys? If you take a look at the home pages of Mandrill, Sendgrid, and Mailgun you can tell they target developers likely because it would be too hard for a non-developer to use their services. After all a developer has to help them set up whatever email they want to send right?

At Zapier we disagree. Sending transactional or automated email should be just as easy for non-technical people as it is for developers and while that may not be the core target of Mandrill, Mailgun or Sendgrid they seem to think so too (all three have added their services via the Zapier developer platform).

Mandrill recently wrote this excellent post about sending custom automated follow up emails for PayPal purchases so that consumers can have some assurances that their purchase order was indeed recieved by the vendor. This is a way better feedback loop for customers than the standard PayPal purchase email that is sent.

If you look down the list of Zap templates you’ll find hundreds of different use cases for sending high value emails just like the PayPal example above.

What Good is Sending Email?

Patio11 says you should probably send more email if you want to make more money. Email is the gold standard for social and productivity. Everyone hates sending email. Automating sending email is great for web services. It should be great for other non-technical services too.

Sidenote: could be aruged this adds to the clutter. Read on for more about this.

Many services have email dropboxes ala Posterous or Basecamp. Entire apps can be built without writing a single line of code by patch working email together with other pre-exisitng apps.

With Great Power Comes Great Responsibility

Sending email isn’t childs play. In the hands of a trained professional email expert is worth it’s weight in gold. Email in the hands of an amatuer will annoy email recipients, kill sender reputation scores, and cause ungodly migraines for those cleaning up the mess.

If you have never sent large amounts of email before I’d encourage, nay I’d insist, you read up on permission. Make sure whoever the recipient is, is happy the email you send reaches them. And don’t just assume they want your email. Explicitily know they want your email.

Remember tools are just that: tools. It’s how you use them that matters. So make sure you use email for good and not evil.

About the Author

Wade Foster is a Co-founder and CEO at Zapier. He likes to write about process, productivity, startups and how to do awesome work.

Visit the updated post here!

Instant Payment Notifications or IPNs let you or your applications get notified of new PayPal transactions. It's pretty cool because now your applications can fulfill orders, refunds when they receive a notification from PayPal.

But if you found this post, odds are you just realized PayPal doesn't let you use more than one IPN and you need to use more than one! Then if you Googled around for a solution you've realized that unless you know a scripting language you're probably out of luck.

Well the good news is there's a pretty simple solution with Zapier.

The Solution

Using Zapier you can setup any number of PayPal to Webhook zaps. Zapier serves as an amplification mechanism for as many IPN URLs as you need.

To get started use this Zap that uses the PayPal "All Transactions" trigger and the WebHook "POST" Action then follow the steps.

  1. For Step 1 give PayPal the Zapier URL (something like https://zapier.com/hooks/paypal/?cid=1234) and place it in your IPN settings for PayPal. Make sure to save the old IPN URL that you are currently using at PayPal.
  2. On Step 2 give Zapier the URL you want PayPal transactions to be sent to and make sure that "Payload Type" is set to "form"
  3. Skip steps 3 and 4 and enable your Zap.
  4. Need to do it with another IPN? Repeat this process, but you can skip step 1 this time around!

Using notification URLs?

Also, a common problem is that your notification_url is set at the button level which overrides the IPN you set in your PayPal settings. This is a simple fix! Just choose one of the below:

  1. Remove the notification_url setting entirely from your button and let the PayPal settings be the default.
  2. Change the notification_url in your code to the Zapier IPN hook URL.

And of course, you can follow the above directions to ensure that each URL gets its notifications.

And that's that! No code and no dealing with PayPal. Let us know if you need any help setting this up.

I've provided a screenshot of what Step 2 in the Zapier flow should look like below for assistance.

Zapier PayPal Webhook

About the Author

Wade Foster is a Co-founder and CEO at Zapier. He likes to write about process, productivity, startups and how to do awesome work.

Get help