MICE Operations icon

MICE Operations

Interact with the MICE Operations API

Actions32

Event → Create Message

AI-generated

Summary

Posts a new message or note on a MICE Operations event via POST /events/{eventId}/messages, with optional subject and author details.

Inputs

  • eventId (required) — Numeric ID of the event to add the message to. It is used in the request URL.
  • eventMessageBody (required) — Message text, sent as message in the request body.
  • eventMessageSubject — Optional subject line, sent as subject.
  • eventCreateMessageType — Either Message or Note. Defaults to Message. Sent as type.
  • eventMessageAuthorId — Numeric author ID, sent as author_id. The default is 0.
  • eventMessageAuthorFirstName — Author first name, sent as author_first_name.
  • eventMessageAuthorLastName — Author last name, sent as author_last_name.
  • eventMessageAuthorEmail — Author email, sent as author_email.
  • requestOptions — Node settings for batching (items per batch and interval), ignoring SSL issues, proxy and timeout (default 10000 ms).

Output shape

The JSON response from the MICE Operations API for the created message, returned as the node's output item.

The source doesn't define the response fields, so they depend on the API. Optional fields that are left empty are still sent with their default values (an empty string, or 0 for Author ID). The node needs the miceoperationsApi credential. Requests go to https://api.miceoperations.com/api/v1.

Examples

Example 1: Log an internal note on an event when a related CRM deal changes.

Event ID = 123, Type = Note, Message = expression with the deal update, Subject = 'CRM update'.

Example 2: Send a message to an event attributed to a specific person.

Event ID = 123, Type = Message, Message = text, Author First Name, Last Name and Email set.

Links

Discussion