Sent Messaging

Operate direct message workflows with messages.send, messages.get, and messages.activities.list.

Establish connection and scope

1. Let the MCP client perform OAuth 2.1/PKCE authorization. Never request, accept, print, or store tokens, API keys, authorization headers, client IDs, or secrets.
2. Surface the organization and Sender Profile selected by the active connection before a mutation. If the client context does not expose both, use sent-account-readiness to inspect the authorized scope before continuing.
3. Reauthorize in the client when the requested organization or Sender Profile differs from the active grant. Do not simulate a scope switch with payload fields.
4. Minimize sensitive output. Mask phone numbers where practical and do not repeat message bodies after the operator has reviewed them.

If MCP is unsupported or authorization fails, keep the skill usable for payload planning. Explain that execution requires a compatible client or reauthorization; never ask the user to paste a credential.

Inspect a message

• Use messages.get for the current record when a message identifier is known.
• Use messages.activities.list for lifecycle events and delivery evidence.
• State that an accepted or queued send is not proof of delivery. Report delivered only when the returned state or activity establishes delivery.
• Return identifiers, timestamps, and status evidence needed to answer the question, masking recipient data and omitting the message body unless it is necessary.