Tokens for cloud service integration

The Revolution admin generates an authorization token and provides it to the cloud service provider. This allows the cloud service provider's product to communicate with your Revolution.

1. Go to Configuration > Integrations > Token.
2. Select New.
3. For Name, enter a descriptive name for the authorization token.
4. For Available in All Sites, enable to allow use of the authorization token for all of your sites or disable to specify a specific Site. If your permissions are limited to single site, Revolution automatically assigns this to your site.

5. For Token Type, select General.

   Refer to Connecting to Social Media Services and Connecting to Collaboration Tools for information about creating tokens for those applications.

   For OAuth, see Creating an OAuth Token.

6. For Token, you will see that Revolution has populated the field with an alpha-numeric string for you to use.

   

7. Select Save.

You can now submit the authorization token string to your cloud service provider, following their processes for communicating with Revolution.

1. Go to Configuration > Integrations > Cloud Service Trigger.
2. Select New > New Cloud Service Trigger.
3. For Name, enter a descriptive name to identify what cloud service this trigger is for.
4. For Available in All Sites, enable to allow use of the trigger for all of your sites or disable to specify a specific Site. If your permissions are limited to single site, Revolution automatically assigns this to your site.
5. TheTrigger ID field will be populated with a unique string after saving your service. It will also appear in the list of Cloud Service Triggers. You can use this ID with the Revolution API. Use the copy icon to easily transfer the information to your clipboard.
6. For Token, select the authorization token you created, or select Create New.

7. (Optional) For Icon, select an icon for scenarios where the cloud service supports displaying it in their product.

   For example, a safety app may support displaying an icon, where as a panic button would not.

8. (Optional) Determine whether you want the users of the cloud service to be able to write notification content on the fly, and whether they can include audio and images.

Tip: You'll need to know whether the cloud service supports adding text, images, and audio from within their product.

• Allow User to Add Text – Cloud service users can write content on the fly. You'll also need to add variables to the notification Message Details, so that the content is pulled into the notification before it is sent to recipients.
• Allow User to Add Images – Cloud service users can attach any image available to them from the product.

• Allow User to Add Audio – Cloud service users can include an existing audio available to them from the product or make a recording, if the product allows it, and include it with the notification.

  Important: When allowing audio to be sent, cloud service trigger must be assigned to a notification type of Stored Audio. If assigned to any other notification type, the audio from the cloud service will not play when the notification is sent.

9. Select Save.

You may repeat these steps to create additional triggers associated with this authorization token

For example, my organization is using both the safety app and personal-carry panic buttons from Company XYZ. I want separate notifications triggered for each. So, I create two triggers, one for the safety app and one for the panic buttons.

As with any trigger, you must assign it to a notification.

1. Create the notification you want sent when triggered from cloud service.
   1. General – Complete this section as you would like. However, you should note that cloud service triggers only support the following notification types: Direct One-Way, Direct Two-Way, Stored Audio, Text and Images, and Text-to-Speech.

   2. Select Triggers – For Activator, select Mobile & 3rd Party. Then for Trigger, select the trigger you created previously.

      

   3. Message Details – Complete this section as you require, but for Title and Body, consider the following:

      • If you are not allowing the cloud service users to enter content on the fly, or the product does not support it, you will need to enter the content you want sent.
      • If you are allowing the cloud service product users to enter text on the fly, you will need to specify, at a minimum, select the following from Add Text Variable:
        • Title – Global > Activator Title, which adds {activatorTitle}

        • Body – Global > Activator Body, which adds {activatorBody}

        These variables use contents entered from the cloud service.

        

        You can also add any static text or other variables.

   4. Endpoint & Contact Selection – Select whatever endpoints and contacts you want to receive the notification.

Create as many cloud service triggers and notifications as you need.

For example, I have one trigger and notification for use with the XYZ Safety app and another trigger and notification for use with the XYZ panic button.