The Twitter spoke ServiceNow has for integrationHub makes it very easy to complete this integration. I was able to get up and running and send my first tweet out in 30 minutes. The Twitter spoke contains one action and it is just called tweet. You can send out a message or media that's it. When I was first getting into this integration I was hoping for a way to consume a tweet or direct message by attaching my Twitter handle to ServiceNow but that was not the case.
I think setting up the Twitter developer account was the longest part of the whole setup. Firstly, you will need a Twitter account. if you do not have one you will need to go through the process of signing up here. Next, you need to make sure you have a verified phone number to access the Twitter developer account. Without having a verified phone number you will not be able to access the API's. The one mistake a made at the very beginning was to not request elevated access, If you forget to request the elevated access don't worry, your flow will let you know
When you press the Apply button at the bottom you will be guided to a form where you will need to answer some questions to get access.
Once access is gained, it's time to set up your project. You have 3 environments to choose from, Development, Staging and Production. Select the environment where you would like to create your project. pick your app name and generate your tokens for the connections
Don't forget you need to update the app permissions so the twitter spoke can write to your account.
Next, generate your keys and tokens and save them someplace safe. You will need them for the ServiceNow portion of this integration. If you haven't done so already, install the Twitter spoke. Once complete, head to integrationHub > Credentials > Click New and you will now see you can add Twitter credentials.
Open flow designer and create a new flow. Set your trigger conditions to whatever table you want. I guess it depends on when you want to send out tweets. Maybe for P1-Critical incidents that affect customers? it could also be when an outage record is created.
To run this create a new P1- Critical incident or just press the test button and select a random P1 incident.
Head to your test Twitter account and see all your hard work pay off. It's a pretty simple solution you can get up and running in 30 minutes.
