MICE OperationsInstall

Summary

Updates an existing event in MICE Operations by sending a PUT request to /events/{eventId} with only the fields you choose to change.

Inputs

• Event ID (required) — Numeric ID of the event to update. It is placed in the request URL.
• Update Fields — Collection of optional fields to change. Each field you add is sent in the JSON body. The fields are: Name (name), Location ID (location_id), Event Type ID (event_type_id), Client ID (client_id), Planner ID (planner_id), Datetime Start (datetime_start), Datetime End (datetime_end), Group Name (group_name), Noticeboard Name (noticeboard_name), Guests (guests), Locale (locale), Reference (reference), Message (message) and Extra Fields (extra_fields, JSON). Datetimes are plain strings, and the node does not declare a format.
• Request Options — Node-level settings for batching (items per batch and interval), ignoring SSL certificate issues, an HTTP proxy, and a request timeout (default 10000 ms).

Output shape

The API's JSON response for the PUT request, one output item per input item. It is presumably the updated event record, but the node doesn't transform the response.

The node applies no post-processing, so the response shape depends on the MICE Operations API. Authentication uses the miceoperationsApi credential against https://api.miceoperations.com/api/v1. HTTP errors fail the node unless Continue On Fail is enabled.

Examples

Example 1: Reschedule an event and change its guest count.

Set Event ID to 123. In Update Fields add Datetime Start, Datetime End and Guests.

Example 2: Reassign an event to a different client and planner.

Set Event ID from a previous node's output. In Update Fields add Client ID and Planner ID.

Links

• n8n community nodes installation guide