MICE Operations icon

MICE Operations

Interact with the MICE Operations API

Actions32

Event → Add Activities

AI-generated

Summary

Adds one or more activities to an existing MICE Operations event by POSTing a JSON array of activity objects to /events/{eventId}/activities.

Inputs

  • Event ID (required) — Numeric ID of the event that receives the activities. It is used in the request URL.
  • Activities (required) — JSON array of activity objects, sent unchanged as the request body. The node doesn't validate the structure. Use the field names the MICE Operations API expects. The Update Activity operation uses fields such as event_timeline_id, location_id, setup_id, datetime_start, datetime_end, name, description, guests, memo and internal_memo.
  • Request Options — Optional node settings: batching (items per batch, batch interval in ms), ignore SSL certificate issues, HTTP proxy, and timeout in ms (default 10000).

Output shape

The parsed JSON response from the MICE Operations API for the POST request, returned as the node's output item or items.

The source doesn't transform the response, and it doesn't document the response schema. Requests are authenticated with the miceoperationsApi credential and sent to https://api.miceoperations.com/api/v1. API errors fail the node unless Continue On Fail is enabled.

Examples

Example 1: Add two timeline activities to event 123.

Event ID = 123. Activities = [{"name":"Welcome drinks","datetime_start":"2026-11-01 17:00","datetime_end":"2026-11-01 18:00"},{"name":"Dinner","datetime_start":"2026-11-01 18:30","datetime_end":"2026-11-01 21:00"}]

Example 2: Create activities from an upstream node's data.

Event ID = {{$json.eventId}}. Activities = {{ JSON.stringify($json.activities) }}

Links

Discussion