The Twitter Data Destination publishes notifications on a Twitter feed using data from a submitted form. This data destination is commonly used to share brief alerts, such as the status of projects or equipment, with other company users.
Data destinations automatically back up data collected in the field. They reduce the need to visit the web portal by making submitted forms available through the services you already use. Different documents can also be sent to different services with a single form submission. Read here for more information on data destinations.
Twitter is a social networking and micro-blogging service that enables users to send and read messages up to 140 characters. Users can access Twitter through the website interface, or they can receive notifications on-the-go through SMS or the mobile app.
- Create the data destination following the instructions here.
- Destination Basics: Name the destination. Optionally choose to auto-link forms and documents to this destination.
- Add Filtering: With a filter set up, form submissions will only be sent through the destination if the filter is met. Read more here.
- Connection: Set up a Twitter Connection or choose an existing connection.
- Set up the Configuration tab as discussed below.
Status Message Expression
Use Data Record Expression Language to create a Tweet using data from your forms. For example, entering “%r was just created by %u” would publish a Tweet with the text “20121212-1812345 was just created by John Doe.”
Note: It is important to incorporate an unique identifier in your Status Message Expression, as Twitter will block repeat status updates. Learn how to create a unique identifier.
Add the Data Record Geostamp to the Tweet
Selecting this will add the location the from is submitted from to the body of the Tweet.
In order for the destination to send any submitted form data, it must first be connected to the form. This is done in the Data Destinations tab of the form builder.
Data destinations should be configured and tested carefully before using them in production. This is key to ensuring that ProntoForms data is received correctly. Please consult the recommendations for testing and troubleshooting data destinations.