Actions32
- Client Actions
- Company Actions
- Event Actions
- External Object Actions
- Invoice Actions
- Location Actions
- Product Actions
- Webhook Actions
Event → Get Messages
AI-generatedSummary
Retrieves the messages and notes attached to a MICE Operations event by sending a GET request to /events/{eventId}/messages, optionally filtered by message type.
Inputs
- Event ID (required) — Numeric ID of the event whose messages are fetched. It is placed in the request URL path.
- Type — Sent as the
typequery parameter to filter messages. Leave empty to omit the filter. Create Message uses 'message' and 'note' as types, but this field is free text. - Request Options — Node-level HTTP settings: batching (items per batch and interval in ms), ignore SSL certificate issues, proxy URL, and timeout in ms (default 10000).
Output shape
The JSON response from the MICE Operations API for the event's messages, returned as output item(s) for each input item.
The source does not define any response transformation or pagination for this operation. The exact response fields come from the API and aren't declared in the node. Authentication uses the miceoperationsApi credential against https://api.miceoperations.com/api/v1.
Examples
Example 1: Fetch all messages and notes for an event.
Resource: Event; Operation: Get Messages; Event ID: 123; Type left empty.
Example 2: Fetch only notes for an event ID taken from a previous node.
Event ID: {{$json.id}}; Type: note.