Prismic

undefined

Detail	Value
Category	CMS
Base URL	https://{repository}.cdn.prismic.io/api/v2
Authentication	Bearer Token
Endpoints	5
Connector key	prismic

Using Prismic in a workflow

1. Go to Connections and click New Connection.
2. Pick Prismic from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET	Search Documents
GET	List Custom Types
GET	Create Custom Type
GET	List Shared Slices
GET	Create Document

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Search Documents

Detail	Value
Operation ID	search_documents_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prismic connection from the Connection dropdown.
3. In the Operation dropdown, select search_documents_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prismic API reference.

GET

List Custom Types

Detail	Value
Operation ID	list_custom_types_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prismic connection from the Connection dropdown.
3. In the Operation dropdown, select list_custom_types_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prismic API reference.

GET

Create Custom Type

Detail	Value
Operation ID	create_custom_type_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prismic connection from the Connection dropdown.
3. In the Operation dropdown, select create_custom_type_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prismic API reference.

GET

List Shared Slices

Detail	Value
Operation ID	list_shared_slices_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prismic connection from the Connection dropdown.
3. In the Operation dropdown, select list_shared_slices_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prismic API reference.

GET

Create Document

Detail	Value
Operation ID	create_document_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Prismic connection from the Connection dropdown.
3. In the Operation dropdown, select create_document_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Prismic API reference.