On This Page
Missive is a team inbox and chat platform that enables your team to collaborate across all communication channels, including emails, SMS, Whatsapp, and more. Missive also allows you to share knowledge and collaborate in real-time on critical customer messages to provide the best response possible.
Missive authenticates API requests from Hevo to access your account data with HTTP Basic authentication.
An active Missive account from which data is to be ingested.
The API Token is available to authenticate Hevo on your Missive account.
You are logged in as an Account Owner or Admin user, to obtain the API token. Else, you can obtain the API token from your account owner or administrator. Read User Types to know about the different types of user accounts in Missive.
Creating the API Token
Hevo uses an API token to authenticate itself on your Missive account.
Perform the following steps to create the API token:
Log in to your Missive account.
In the left navigation pane, click on the username displayed at the left bottom of the Missive UI.
Click Settings and then select API.
In the API window, click Create new token.
Specify a unique name for this API Token, and click OK.
Copy the API token and save it securely like any other password.
You have successfully created your API token. Use this token for creating Hevo Pipelines.
Configuring Missive as a Source
Perform the following steps to configure Missive as the Source in your Pipeline:
Click PIPELINES in the Asset Palette.
Click + CREATE in the Pipelines List View.
In the Select Source Type page, select Missive.
In the Configure your Missive Source page, specify the following:
Pipeline Name: A unique name for the Pipeline, not exceeding 255 characters.
API Token: The API Token that you obtained and copied from your Missive account.
Click TEST & CONTINUE.
Proceed to configuring the data ingestion and setting up the Destination.
|Default Pipeline Frequency||Minimum Pipeline Frequency||Maximum Pipeline Frequency||Custom Frequency Range (Hrs)|
|1 Hr||1 Hr||24 Hrs||1-24|
Note: You must set the custom frequency in hours as an integer value. For example, 1, 2, 3 but not 1.5 or 1.75.
Historical Data: In the first run of the Pipeline, Hevo ingests all historical data for all the objects except Contacts and loads it to the Destination.
Incremental Data: Once the historical load is complete, all new and updated records for the Contacts object are synchronized with your Destination as per the Pipeline frequency.
Pagination: An API response for each Missive object fetches one page with up to 200 records, except the response for the Conversations and Conversation messages object, that can contain up to 50 records and 10 records per page respectively.
Rate Limit: Missive imposes a limit of a maximum of 300 requests per minute to ensure that their system remains stable for usage by all users.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination database:
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
|Contact Books||Full Load||Contains the details about where you store and manage all of your contacts. Each contact is assigned a unique ID and can be shared among the teams.|
|Contacts||Incremental||Contains the details of a person or entity with whom you have communicated.|
|Conversations||Full Load||Contains the details of all the replies as well as notes added to a ticket. Notes are non-invasive ways of sharing updates about a ticket amongst teams and customers.|
|Conversation Messages||Full Load||Contains the details of all the messages exchanged between user and agents.|
|Shared Labels||Full Load||Contains the details of all the team conversations in an organized order by assigning IDs to them.|
|Users||Full Load||Contains the details of all the users that have access to the missive account.|
|Teams||Full Load||Contains the groups of related projects and people within an organization.|
|Organizations||Full Load||Contains the details of group of people who collaborate together in an organization.|
Hevo currently does not support deletes. Therefore, any data deleted in the Source may continue to exist in the Destination.
The data is loaded in Incremental Load in each Pipeline run. As a result, you cannot load the historical data alone at any time.
Refer to the following table for the list of key updates made to this page:
|Date||Release||Description of Change|