Missive

Missive is a team communication and collaboration platform that brings email, SMS, WhatsApp, and other channels into shared inboxes. Its REST API exposes contacts, conversations, messages, tasks, teams, and organizations, letting you sync collaboration data into Nexla and push outbound messages, posts, drafts, and contact updates back into Missive.

Power end-to-end data operations for your Missive API with Nexla. Our bi-directional Missive connector is purpose-built for Missive, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Missive or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Missive workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Missive credential, you need a Missive API token. Missive authenticates REST API requests with a personal API token sent as a Bearer token in the Authorization header, and all requests are directed at the API base URL (by default https://public.missiveapp.com/v1).

To obtain a Missive API token, follow these steps:

1. Sign in to Missive with an account that belongs to an organization on the Productive plan. API tokens can only be generated by organizations on this plan.

2. Open your account Preferences (settings) in the Missive app.

3. Navigate to the API section of your preferences.

4. Select the option to create a new API token, give it a descriptive name (e.g., "Nexla Integration"), and generate the token.

5. Copy the generated token and store it securely. The token grants access to your Missive data based on your account's permissions and should be treated as sensitive information.

The token is sent in the Authorization header as Bearer <your-token> on every API request. If a token is compromised, revoke it from the API section of your Missive preferences and generate a new one. For detailed information about the API and available endpoints, refer to the Missive REST API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Your Missive API key for authentication.
Base URL	Yes	No	The base URL for the Missive API.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Missive API key in the API Key field. This is the personal API token you generated in Prerequisites and is sent as a Bearer token in the Authorization header for all API requests.

4. Enter the Missive API base URL in the Base URL field. Unless you have been directed to a different host, use https://public.missiveapp.com/v1.

   Your Missive API token grants access to your Missive data and should be kept confidential. If the token is compromised, revoke it in the API section of your Missive preferences and generate a new one.

   For detailed information about authentication and available endpoints, see the Missive REST API documentation.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Missive connector tile, then select the credential that will be used to connect to the Missive instance, and click Next; or, create a new Missive credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Missive endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Contact Books

Returns a list of all contact books in the organization.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

[Rest API] List Contacts

Returns a list of all contacts in the organization.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

[Rest API] List Contact Groups

Returns a list of all contact groups in the organization.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

[Rest API] List Users

Returns a list of all users in the organization.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

[Rest API] List Teams

Returns a list of all teams in the organization.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

[Rest API] List Shared Labels

Returns a list of all shared labels in the organization.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

[Rest API] List Organizations

Returns a list of all organizations accessible to the authenticated user.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

[Rest API] List Conversations

Returns a list of all conversations in the organization.

This endpoint uses cursor-based pagination keyed on each conversation's last activity timestamp. Nexla automatically follows the cursor to ingest all available conversations.

[Rest API] Retrieve a single conversation by ID

Retrieve a single conversation by ID including full metadata, assignees, labels.

This endpoint requires a Conversation ID parameter identifying the conversation to retrieve. Enter the unique identifier of the conversation when configuring the source.

[Rest API] List Tasks

Returns a list of all tasks in the organization.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

[Rest API] List Messages

Returns a list of messages in the organization.

This endpoint uses offset-based pagination. Nexla automatically pages through the results to ingest all available records.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Missive data sources can also be manually configured to ingest data from any valid Missive REST API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Missive data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Missive destination, and select the Send to Destination option from the menu. Select the Missive connector from the list of available destination connectors, then select the credential that will be used to connect to the Missive organization, and click Next; or, create a new Missive credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Missive endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Send outbound messages

Send outbound messages (email/SMS) directly without a draft step.

Each record from your Nexset is sent as a JSON request body to create a message. The record structure must match the format expected by the Missive messages endpoint.

[Rest API] Create a post

Create a post in a new or existing conversation; also the primary mechanism to perform conversation actions (close, assign, add labels, move to inbox) from integrations.

Each record from your Nexset is sent as a JSON request body to create a post. The record structure must match the format expected by the Missive posts endpoint.

[Rest API] Create contacts

Create new contacts in a contact book, enabling CRM sync flows.

Each record from your Nexset is sent as a JSON request body to create a contact. The record structure must match the format expected by the Missive contacts endpoint.

[Rest API] Create drafts

Create and optionally send email, SMS, WhatsApp, or Live Chat drafts in new or existing conversations.

Each record from your Nexset is sent as a JSON request body to create a draft. The record structure must match the format expected by the Missive drafts endpoint.

[Rest API] Create tasks

Create and manage tasks programmatically within Missive conversations.

Each record from your Nexset is sent as a JSON request body to create a task. The record structure must match the format expected by the Missive tasks endpoint.

[Rest API] Create teams

Create new teams within an organization.

Each record from your Nexset is sent as a JSON request body to create a team. The record structure must match the format expected by the Missive teams endpoint.

[Rest API] Update a contact

Update an existing contact's fields (name, phone, email, group memberships).

This endpoint requires a Contact ID parameter identifying the contact to update. Each record from your Nexset is sent as a JSON request body with the updated fields.

[Rest API] Update a team

Update team name, emoji, and active members.

This endpoint requires a Team ID parameter identifying the team to update. Each record from your Nexset is sent as a JSON request body with the updated fields.

[Rest API] Delete a contact

Delete a contact from a contact book.

This endpoint requires a Contact ID parameter identifying the contact to delete. Each record from your Nexset triggers a delete request for the specified contact.

Manual configuration

Missive destinations can also be manually configured to send data to any valid Missive REST API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Missive APIs expect JSON format for write operations. For update operations, include the ID of the object to be updated at the end of the endpoint URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Missive endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Missive endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.