Content Fetch action
Reads one record, by id or by a field the type uses as a unique key. In the action picker it is Content Fetch, under General Actions. With no connection it reads this workspace's records; with a Brightspot connection, content in that CMS.
Fields
| Field | Required | Description |
|---|---|---|
| Connection | No | Leave empty for this workspace's records. Pick a Brightspot connection to read from that CMS. |
| Site | No | Shown only for a Brightspot connection: the site to act on. Blank means the connection's site when it pins exactly one, otherwise every site the connection reaches. |
| Content Type | Depends | Required to fetch by any field other than the id. Optional when fetching by id, where it rejects records of any other type. |
| Lookup Field | No | The field to match on. Leave blank to fetch by content id; pick an indexed unique field, such as a slug or an external id, to fetch by that instead. |
| Lookup Value | Yes | The value to match. A content id when Lookup Field is blank. Accepts variables. |
| Revision | No | One of the content's unpublished revisions or past versions to read instead of the content as it stands, usually bound to a trigger's Revision › ID. Leave it blank, and the placeholder reads Current, for live content, or the draft if it was never published. A workspace record has versions only. |
Output
| Field | Description |
|---|---|
found | Whether a record matched. |
contentId, contentTypeId, contentTypeName, label | The record's identity, when found. |
values | The record's field values, when found: those of the revision or version read. A field of the content type that the record leaves unset is there as null. In a workspace the fields are declared by name, so later steps can pick them. |
revision | Which revision the values are: its kind (LIVE, DRAFT, REVISION or VERSION), id, name, status, workflow state, schedule, who saved it and when, and previousVersionId, the version saved before it, which a Content Compare can compare against. See Revisions. |
pendingRevisions | The content's unpublished revisions, newest first, each described the same way. It answers whether the content has work waiting to be published, and which revision is the newest, without a separate step. Revisions of variations and archived revisions are left out. |
Bound to a trigger's Revision › ID, a Fetch follows what the editor or the event was on: a revision's values when there is one, and live when the trigger fired on live content, where the binding resolves to nothing. A revision's values are live with the revision's changes merged, which is what the content will be once it publishes. A revision or version of other content is refused, as is a revision of a variation.
A fetch by id that finds nothing fails the step: an id names a record that is supposed to exist. A fetch by any other field that finds nothing reports found: false and continues, since asking whether anything holds a value yet is exactly what a later Save with Create If Missing wants to know. More than one match fails, because the field was supposed to be unique.