MICE OperationsInstall

Summary

Updates a single activity on a MICE Operations event by sending a PUT request to /events/{eventId}/activities/{activityId} with only the fields you choose to change.

Inputs

• eventId (required) — Numeric ID of the event that owns the activity. Used in the request URL.
• activityId (required) — Numeric ID of the activity to update. Used in the request URL.
• eventUpdateActivityFields — Collection of optional fields to change. Each field you add is sent in the JSON body. Options: Event Timeline ID (event_timeline_id), Location ID (location_id), Setup ID (setup_id), Datetime Start (datetime_start), Datetime End (datetime_end), Name (name), Description (description), Guests (guests), Memo (memo), Internal Memo (internal_memo). Datetimes are plain strings, and the node doesn't declare a format.
• requestOptions — Node-level HTTP settings: batching (items per batch and interval in ms), ignore SSL issues, proxy, and timeout (default 10000 ms).

Output shape

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

The node applies no post-processing to this operation, so the response shape is whatever the API returns. Authentication uses the miceoperationsApi credential against https://api.miceoperations.com/api/v1. The source doesn't show the response fields.

Examples

Example 1: Reschedule an activity to a new time slot

Set Event ID and Activity ID, then add Datetime Start and Datetime End in Activity Update Fields.

Example 2: Update guest count and internal notes for an activity

Set Event ID and Activity ID, then add Guests and Internal Memo in Activity Update Fields.

Example 3: Move an activity to another location

Set Event ID and Activity ID, then add Location ID in Activity Update Fields.

Links

• n8n community nodes installation guide