Actions39
- Datastore Create
- Datastore Search
- Datastore Upsert
- Group Activity List
- Group Create
- Group Delete
- Group Member Create
- Group Member Delete
- Group Package Show
- Group Patch
- Group Purge
- Group Show
- Group Update
- Organization Create
- Organization Delete
- Organization List
- Organization Member Create
- Organization Member Delete
- Organization Patch
- Organization Purge
- Organization Show
- Organization Update
- Package Activity List
- Package Create
- Package Delete
- Package List
- Package Patch
- Package Search
- Package Show
- Package Update
- Recently Changed Packages Activity List
- Resource Create
- Resource Patch
- Resource Search
- Resource Show
- Resource Update
- Status Show
- Tag List
- User List
Organization List
AI-generatedSummary
Lists organizations registered on the CKAN instance. By default, returns organization name slugs; enable All Fields to return organization objects, with optional dataset counts, extras, and users.
Inputs
- CKAN URL (required) — URL of the CKAN instance, such as https://demo.ckan.org.
- Sort — Sort field and direction, such as "title asc" or "name desc". The operation declares a default sort of "title asc".
- Limit — Maximum number of organizations to return; defaults to 1000.
- Offset — Number of organizations to skip for pagination; defaults to 0.
- All Fields — When enabled, requests full organization objects instead of name strings; defaults to false.
- Include Dataset Count — When All Fields is enabled, requests the dataset count for each organization; defaults to true.
- Include Extras — When All Fields is enabled, requests each organization's extra fields; defaults to false.
- Include Users — When All Fields is enabled, requests each organization's user list; defaults to false.
Output shape
One item per input item, containing {"success": true, "data": ...}.
The data is the CKAN response result: a list of organization slugs by default, or organization objects when All Fields is enabled. Results are paginated with Limit and Offset. This GET operation does not require CKAN API credentials; the node checks the instance with status_show before requesting the list.