The information in this article is the intellectual property of xMatters and is intended only for use with xMatters products by xMatters customers and their employees. Further, this intellectual property is proprietary and must not be reused or resold.
This integration combines the power of xMatters with Twitter: when tweets meeting predetermined criteria occur, this combination leverages your group on-call schedules and rotations, escalation rules, user device preferences and timeframes to send the right message to the right members of your team on the right device at the right time. It also supports targeted push, voice, SMS and email notifications, and self-managed subscriptions to events, enabling you to stay informed.
- Reduce the unknown when key tweets are made about things that are important or key transactions are detected.
- Self-service and managed subscriptions allow business stakeholders to remain informed when tweets occur.
- xMatters design tools allow specific message content to be tailored to different device types.
This integration uses Zapier, which provides access to a number of pre-built integration points - including xMatters On-Demand.
Before you start...
You need some things before you start:
- An account and login information for Zapier.
- An account and login information for Twitter.
- Access to your xMatters deployment, and the ability to create communication plans.
Before configuring anything in Twitter, you'll need to configure xMatters.
This integration requires a user who can authenticate REST web service calls when working with events – these permissions are provided by the "REST Web Service User" role in xMatters.
For Free and Trial customers, your system has an "Integration User" already configured with the REST Web Service User role, so you don't need to burn up an extra user from your limited supply. Make sure you've changed this user's password from the default, then you're good to go.
For everyone else, we recommend you create a user specifically for this integration because this user appears as the initiator or submitter of events from the integration (in messages, the Communication Center, event reports, etc.). Give this user the "REST Web Service User" role and a profile that lets you easily identify the user as specific to the integration – for example:
- User ID: twitter
- First name: Twitter
- Last name: Integration
Note: Make sure you keep the user ID and password of this user handy. You'll need them when configuring other parts of this integration.
Each user or group that you want to be able to receive notifications must exist in xMatters before you can target them.
You can create multiple groups and users at once using the EPIC feature.
The next step is to import the Twitter communication plan.
To import the communication plan:
- Download the attached ZIP file to your system.
- In the target xMatters system, on the Developer tab, click Import Plan.
- Click Browse, and then locate the downloaded ZIP file.
- Click Import Plan.
- Once the communication plan has been imported, click Plan Disabled to enable the plan.
- Click Edit > Forms.
- For the Twitter Search form, in the Not Deployed drop-down list, click Create Event Web Service.
- After you create the web service, the drop-down list label will change to Web Service Only.
- In the Web Service Only drop-down list, click Permissions.
- Enter the integration user, and then click Save Changes.
- Click Edit > Layout.
- On the Layout tab, in the Recipients section, specify the users or groups you want to receive notifications.
- Click Save Changes.
To retrieve the web service URL for a form:
- On the Forms tab, In the Web Service Only drop-down list, click Access Web Service URL. Copy the highlighted URL at the top of the dialog box.
- The Access Web Service URL option appears twice in the drop-down menu. Ensure that you click the option just below Create Event Web Service.
Now that you've configured xMatters, it's time to configure Zapier to connect to Twitter.
Create a Zap
- Login to Zapier, and then click Make a New Zap.
- In Step 1: Choose a trigger and action:
- In the "When this Happens" area, select Salesforce as the trigger. For the action, select New Case.
- In the "Do This" area, select xMatters as the trigger. For the action, select Create Event.
- In Step 2: Select a Twitter account, click Connect a Twitter Account. Add the Twitter account that you want to use for the integration, and authorize the app. Once the app is authorized, click Continue.
- In Step 3: Select an xMatters account, log in to your xMatters instance using the integration user. Then click Continue.
- In Step 4: Filter Twitter triggers, enter the search terms and filters you want to notified about. You can search for words, mentions, account information, or any other content. You can also add any number of customer filters to narrow your search mentions. When you're done, click Continue.
- In Step 5: Match up Twitter Search Mentions to xMatters, paste the web service URL from the form in xMatters into the Web Service URL field, and then modify the URL to include the username and password of the REST API user.
For example, change:
- In the Properties section, use the drop-down lists to match properties:
- In Step 6: Test this Zap, click Test Twitter Search.
- In Step 7: Name and turn this Zap on, name and save the Zap.