MICE OperationsInstall

Summary

Creates a new event in MICE Operations by sending a POST request to /events at https://api.miceoperations.com/api/v1 with the supplied fields as the JSON body.

Inputs

• Name (required) — Event name, sent as name.
• Location ID — Numeric ID of the location, sent as location_id. Defaults to 0.
• Event Type ID — Numeric event type ID, sent as event_type_id. Defaults to 0.
• Client ID — Numeric ID of the client, sent as client_id. Defaults to 0.
• Planner ID — Numeric ID of the planner, sent as planner_id. Defaults to 0.
• Datetime Start — Start date and time as a string, sent as datetime_start. The source declares no format.
• Datetime End — End date and time as a string, sent as datetime_end. The source declares no format.
• Group Name — Sent as group_name.
• Noticeboard Name — Sent as noticeboard_name.
• Guests — Number of guests, sent as guests. Defaults to 0.
• Locale — Locale string, sent as locale.
• Reference — Reference string, sent as reference.
• Message — Message text, sent as message.
• Extra Fields — JSON value (default []), sent as extra_fields.
• Request Options — Node settings for batching (items per batch, interval), ignoring SSL issues, proxy and timeout (default 10000 ms).

Output shape

The JSON response from the API for the POST /events call. This is presumably the created event record, but the source doesn't define its fields.

No post-processing is applied. Optional fields left at their defaults (0 or empty string) are still sent in the body, because there is no filtering for body fields. Requires the miceoperationsApi credential.

Examples

Example 1: Create a booked event for a known client and location

Name='Annual Conference', Client ID=12, Location ID=3, Datetime Start and Datetime End set, Guests=150.

Example 2: Create a minimal placeholder event

Set only Name='Team Offsite' and a Reference like 'CRM-1042'; leave the other fields at their defaults.

Links

• n8n community nodes installation guide