For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
    • Overview
    • API Credentials
    • Errors
    • Legacy & Deprecated APIs
  • Events API
    • Chat Markup
    • Rate Limits
    • Message Delivery
  • (Beta) Conversations API
  • Data API
    • GETList conversations
    • GETList interactions
    • GETList plugins calls
    • GETList Plugin Resources
    • GETList Users
  • Webhook Listeners
  • Content Gateway
    • Overview
    • Integration Strategies
    • Starter Code
    • Verifying Your Build
    • Connecting Your Gateway to Moveworks
    • Authentication
    • How Permissions Work
    • Common Pitfalls
    • Operational Guide
    • Errors
    • Supported MIME Types
  • Legacy Gateways
    • Authentication
    • Response Options
    • Field Types
    • Form Gateway Errors
DeveloperAcademyCommunityStatus
On this page
  • Delivery Experience
  • Delivery Reliability
Events API

Message Delivery

||View as Markdown|
Was this page helpful?
Edit this page
Previous

List conversations

Next
Built with

Delivery Experience

Messages are delivered to the user’s preferred chat platform. The preferred chat platform is determined by the last place that the user sent a message to Moveworks.

If you have deployed the Embedded Assistant, messages will be delivered to both the preferred chat platform and the Embedded Assistant.

Messages do not respect business hours.

Delivery Reliability

When you make an API call to the Events API, the following actions are taken before returning:

1

Token validation

The API token is validated.

2

Payload validation

The HTTP payload is validated against size constraints.

3

Email validation

Moveworks performs a syntactical validation of all emails.

4

Recipient verification

Moveworks cross-checks the list of recipients to ensure they exist and are allowlisted.

5

Message scheduling

Moveworks immediately schedules the messages for delivery.

Depending on your request volume, your message may take a few minutes to be delivered. This is because chat platforms, like Teams & Slack, limit the number of messages that can be sent per minute.

Asynchronous Delivery

Even though messages are scheduled immediately, they are delivered asynchronously. This means the message can still fail under the following cases (non-exhaustive):

  • The user’s email does not exist in your organization’s identity system
  • The user blocked the bot
  • The chat platform timed out (note: Moveworks does apply retries for failure tolerance)