Create draft with the Front API

Creates a draft reply to the last message of a conversation, for a teammate to review and send in Front. Nothing is sent. A private draft is visible only to its author, so set author_id to the teammate who will review it, or use mode shared.

Identifier
front_create_draft

The request

POST https://connect.reportei.com/api/tools/front_create_draft/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "conversation_id": "<conversation_id>",
    "channel_id": "<channel_id>",
    "body": "<body>"
  }
}

Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.

Parameters

ParameterTypeRequiredDescription
conversation_idstringYesId of the conversation, starting with cnv_, from Search conversations.
channel_idstringYesChannel the draft will be sent from: the id starting with cha_ from List channels, or alt:address: followed by the channel address, like alt:address:support@acme.com.
bodystringYesBody of the draft. Email channels accept HTML.
author_idstringNoTeammate who owns the draft: the id starting with tea_ from List teammates, or alt:email: followed by the teammate email. Omit it to create the draft as the API token.
modestringNoprivate, the default, shows the draft only to its author; shared shows it to every teammate with access to the conversation.Values: private, shared
toarrayNoRecipient handles, like email addresses, for when the draft is sent.
ccarrayNoHandles that get a copy when the draft is sent.
bccarrayNoHandles that get a blind copy when the draft is sent.
subjectstringNoSubject of the draft.

Supported connections

Your customer connects their Front account once, with one of the modes below. The same connection serves every tool of the toolkit.

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

The response

On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.

Ready for AI agents

This tool's input is a JSON Schema, available at GET /api/tools/front_create_draft. It becomes your agent's tool definition with no conversion.

Other Front tools

See all 13 tools

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.