BulkGate Helpdesk
  • Languages iconEnglish
    • Czech

›Integration guidelines

Integration guidelines

  • Getting started with Zapier
  • Zapier BulkGate integration

Delivery report webhook

  • Setup

Zapier BulkGate integration

Zapier BulkGate integration

This document will guide you through Zapier Zap creation

1. Zap creation

The main purpose of Zapier is to connect apps in order to complete a particular task. Such connection is called Zap. After accepting invitation you will be send to the Zapier site where you will click the Make Zap button.

2. Choosing Zap trigger

Every Zap needs an app that will activate the rest of the apps included in a Zap. Because BulkGate integration does not contain any triggers, we need to choose any other app that will work as a starting point of our Zap. In our example we are going to use the integration of Gmail.

Choose trigger

1. Choosing trigger

In our example we are going to create a Zap that will be activated every time we receive an email on a particular email address. Every trigger, or action requires set of parameters to function properly. New email trigger requires connection to an email account and inbox.

New email

2. Testing

Every trigger/action requires test of functionality. Without such test it's not possible to propagate data to the next step. Test works as follows. Zapier will check the specified inbox to test its availability. Content of returned message will be available for propagation to the next step.

3. BulkGate integration

Now that we have trigger set up, we will connect BulkGate integration. Our example is as follows. After receiving an email an SMS notification will be send to a specified phone number.

1. Select application

We choose BulkGate as a second step app.

BulkGate

2. Select action

We choose Send transactional SMS action.

Choosing action

3. Authentication

We need to specify authentication information (Application ID, Application token). To acquire such information visit BulkGate Api setup guide.

Authentication

4. Input parameters

We will insert input parameters required to send transactional SMS. For additional information concerning of input parameters visit BulkGate API documentation.

Transactional SMS parameters

5. Transaction message test

Now we can test functionality of the second step of our Zap, which means sending a test SMS based on said parameters.

Transaction test

6. Delivery report

Our Zap now functions as follows. If we receive an email, notification SMS will be send out. We will then expand the functionality by receiving a delivery report by clicking the Add step button and choose BulkGate app with Get delivery report action.

Delivery report

7. Test delivery report

This action requires SMS ID passed down from second step. Now we test this step by receiving a delivery report from SMS send in previous step.

Delivery report test

8. Ready to use

Zap is now complete and we can name it as needed. After activation, Zapier will check email inbox every 15 minutes. If Zap cannot be activated, it is because every Zap including more than two steps needs a Premium/trial account to work.

Naming zap

← PreviousNext →
  • 1. Zap creation
  • 2. Choosing Zap trigger
    • 1. Choosing trigger
    • 2. Testing
  • 3. BulkGate integration
    • 1. Select application
    • 2. Select action
    • 3. Authentication
    • 4. Input parameters
    • 5. Transaction message test
    • 6. Delivery report
    • 7. Test delivery report
    • 8. Ready to use
SolutionsSMS GatewayViber for BusinessBroadcastBulk SMSSMS NotificationsTwo-way SMSSmart SMSMobile ConnectWeb Portal
Partners & DevelopersSMS APIIntegrationsAffiliate programWhite label
SourcesBlogYouTubeFacebookLinkedInTwitterGitHubPackagist
CompanyContactPrivacyTerms and Conditions
Price listsPrice list SMSPrice list ViberPrice list Mobile Connect
SMS GatewayTOPefekt s.r.o. © 2022