The Progressier Push API is a convenient way to send push notifications to users programmatically. But if you're not technical, integrating it into your existing app may be challenging.
That's why the API now comes as a Zapier action! Zapier allows you to seamlessly connect thousands of apps and platforms without code. For example, you can...
Notify all users when you publish a new post on your WordPress site
Send a notification to a specific user when a new row is added to a Google sheet
Send a push notification every day at a given time
Get started
Progressier's Push API is currently available in beta. If you don't have a Zapier account yet, create one now. Then click on the following link to unlock access to the Progressier integration: https://zapier.com/developer/public-invite/186359/06f1f60071f8ad6461f598bf6fcd0217/
Click Accept Invite & Build a Zap to add it to your account.
In the Zapier dashboard, click on Create to create a new Zap.
The next step is configuring the Trigger. A trigger is the event that will kickstart your workflow. There are many different ones you can choose from. In this example, we'll choose Zapier Tables, which are very similar to Airtable or Google Sheets. This zap will automatically send a push notification whenever we add a new record to our table.
Next, you'll need to choose an Action. If you've accepted the invitation at step 1, type Progressier and you should have the option to add it as an action. Select Progressier.
5. Under Event, select Send Push Notification, then click Continue.
6. The next step is authenticating to the Progressier API with your API key. You'll find your API key at API Documentation > API Key in the Progressier dashboard. Click on Choose in the Choose an Account section, then Connect a new account.
7. A new window tab should open. Enter your API Key in the first field, and the name of your app in the second field. The App Name field is really just for your own convenience. This is useful for organizing your apps if you're going to send push notifications to multiple Progressier apps in different Zaps. Finally, click on Yes, Continue to Progressier button.
8. Now open the Action section. There are four mandatory parameters:
recipients is how you specify who to send the notification to. You can send the notification to a user by specifying their email, to all your users, to a specific list of users, or to users that match specific criteria. Check out the official API documentation for all available options.
title is a string of text up to 50 characters that typically identifies the sender of the notification
body contains the details of the push notification
url specifies where users will be taken when they click on the notification
Other parameters aren't mandatory. You can leave them empty for now.
9. In the screenshot above, we've filled out each of the mandatory parameters with static content. But in most cases, you'll want to retrieve content from the trigger, which you can do by simply clicking on the field. Here is what it might look like with our Zapier Tables example:
And for reference, this is what our matching Zapier Table looks like:
Whenever we create a new record in that table, the workflow/zap will be processed, and the Action we've set up will be executed with content from that particular new record. Convenient!
10. Now, open the Test tab. Note that clicking Test action will actually send a push notification. Make sure that you've properly set the recipients parameter so that only your test devices receive the notification you're about to send.
11. If your notification contains an error, you'll see a descriptive error message that tells you exactly what was wrong with your request. You can also see a log of all your failed and successful requests in the Push Notifications section of the Progressier dashboard.
12. If your notification was successful, you'll see a success message. At this point, you're pretty much done. All that's left is to publish your Zap!
If you have comments or feedback, please reach out using the widget at the bottom-right corner of this page.