Actions15
Overview
This node integrates with the DatoCMS API to manage content records. Specifically, the Record - Publish operation allows users to publish a record in DatoCMS by its ID. Publishing a record makes it publicly available or visible according to the CMS's workflow.
Typical use cases include:
- Automating content workflows where records are created or updated and then published automatically.
- Integrating DatoCMS content publishing into larger automation pipelines.
- Triggering publication of specific records based on external events or conditions.
For example, after creating or updating a blog post record via this node, you can immediately publish it so that it becomes live on your website.
Properties
| Name | Meaning |
|---|---|
| Item Type | The type of item (content model) in DatoCMS to work with. You can select from a list or specify an ID. |
| Record ID | The unique identifier of the record to publish. This is required to identify which record to publish. |
Output
The output JSON contains the full data of the published record as returned by the DatoCMS API. This includes all fields of the record after publication.
- The output is structured as a JSON object representing the record.
- There is no binary data output for this operation.
Example output snippet (simplified):
{
"id": "record-id",
"item_type": { "id": "item-type-id", "type": "item_type" },
"field_1": "value",
"field_2": "value",
"_published_at": "2024-01-01T12:00:00Z",
...
}
Dependencies
- Requires an API key credential for authenticating with the DatoCMS API.
- The node uses the official DatoCMS Node.js client library internally.
- No additional environment variables are needed beyond the API token and optional environment name configured in credentials.
Troubleshooting
Error: Missing or invalid Record ID
Ensure the "Record ID" property is provided and correctly references an existing record.Error: Insufficient permissions
The API key used must have permission to publish records in the target DatoCMS project.Error: Record not found
Verify that the record ID exists and belongs to the specified item type.General API errors
Network issues or invalid API tokens will cause failures. Check connectivity and credential validity.If the node is set to continue on fail, errors will be returned in the output JSON under an
errorfield.