Actions60
- Organization Actions
- Building Actions
- Resident Actions
- Channel Actions
- Message Actions
- Post Actions
- Event Actions
- Poll Actions
- Incident Actions
- Asset Actions
- Booking Actions
- Classified Actions
- Document Actions
- Notification Actions
- Council Project Actions
- Council Vote Actions
- Council Meeting Actions
- Council Task Actions
Event → Get Many
AI-generatedSummary
Retrieve a list of events from the Nido Property Management API, optionally filtered by status, upcoming, or past status, with pagination and result-limiting controls.
Inputs
- filters — Filter events by status, upcoming, or past status. Status options: Draft, Published, Cancelled, Completed. Default status filter is 'published'. 'upcoming' and 'past' are booleans to narrow by timing.
- returnAll — Whether to return all results or only up to a given limit. Default: false.
- limit — Maximum number of results to return (1-100). Only applied when 'returnAll' is false. Default: 25.
Output shape
When 'returnAll' is false (default), returns up to 'limit' event objects from the first API page. When 'returnAll' is true, returns all available event objects paginated in groups of 100 until fewer than 100 remain. Filters are passed as query parameters to the /events endpoint.
No additional runtime side effects beyond the API fetch. The node outputs an array of event JSON objects (or a single object if only one is returned by the API).
Examples
Example 1: Get up to 10 published events, ignoring upcoming/past filters.
Set 'Limit' to 10, leave 'Return All' false, set 'Filters' -> 'Status' to 'published'.
Example 2: Get all events created in the last month.
Set 'Return All' true, leave filters unset or adjust as needed; the API pagination will retrieve the full result set.