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
Package Create
AI-generatedSummary
Create a dataset on the specified CKAN instance by sending its metadata to the CKAN package_create action. The operation requires an API token and returns CKAN’s created dataset record.
Inputs
- CKAN URL (required) — URL of the CKAN instance, such as
https://demo.ckan.org. - Name (required) — URL-safe dataset slug: 2–100 lowercase letters, numbers, hyphens, or underscores.
- Title — Human-readable title; CKAN defaults it to the name if omitted.
- Notes — Dataset description; Markdown is supported.
- Owner Org — Owning organization ID or name. Most CKAN instances require one unless unowned datasets are allowed.
- License Id — License identifier, such as
cc-byorodc-pddl. - Tags — JSON array of tag objects, such as
[{"name":"environment"}]. - Private — Whether the dataset is visible only to members of its owning organization. Defaults to false.
- State — Dataset state, such as
activeordeleted; CKAN documentsactiveas the default. - Extras — JSON array of additional metadata objects, such as
[{"key":"region","value":"EU"}]. - CKAN API credentials (required) — Configure the CKAN API token credential; this POST operation fails if no token is available.
Output shape
One n8n item per input item, containing { "success": true, "data": <created dataset record> } on success.
The node sends the supplied dataset fields as the request body. With Continue On Fail enabled, a failed input instead yields an item containing an
errormessage.