Exporting Content to TerminalFour

Updated 28 July 2026 5 min read

TerminalFour is a CMS designed for higher education. Its site structure is built from sections, and each section can contain multiple pieces of content. Each piece of content uses a content type, which defines the content structure.

Before setting up this integration, it is a good idea to read Understanding Integrations first.

Adding Credentials

To create an integration with TerminalFour, you need to provide the following integration credentials:

  • TerminalFour API URL. This is commonly the URL for your Terminalfour instance with /rs appended to the end. For example, https://my-website.com/terminalfour/rs.
  • Authentication Token. You can create an authentication token within TerminalFour, or alternatively ask an Administrator to help you.

You can add these credentials by:

  1. Open the Integrations: Select Integrations in the project navigation.
  2. Open or create your TerminalFour integration: Choose the integration you want to configure.
  3. Click the Settings button to open the integration settings.
  4. In the top menu, click the options button .
  5. From the dropdown, select Manage TerminalFour Credentials .
  6. Provide your credentials, including your TerminalFour API URL and Authentication Token.
  7. Save your credentials by clicking "Save Credentials".

Once you save those credentials, CollectContent will automatically try to retrieve the Content Types available on your TerminalFour instance. These content types are used to map CollectContent data to the correct TerminalFour fields.

If CollectContent cannot reach your TerminalFour instance, you will be shown an error message with the option to "Retry" or to "Manage Credentials".

You can update your credentials at any time, for example, if your authentication token expires.

Build the export flow

Exporting to TerminalFour uses a nested flow of action blocks. Action blocks perform a particular action, such as creating a section in TerminalFour. You construct the flow you need for your integration.

For example, you may wish to a create section in TerminalFour for each piece of content you have in CollectContent. Then within each of these new TerminalFour sections, you can add a TerminalFour Content Type pre-filled with your content.

You can build an export flow by:

  1. Open the Integrations: Select Integrations in the project navigation.
  2. Open the TerminalFour integration: Choose the integration you want to configure.
  3. Add the blocks you need: Build your export flow by clicking the "Add Action" button. Actions can be nested within each other. For example, if you nest a "Create TerminalFour Section" within a "For each piece of Content" block, then a new TerminalFour section will be created for each piece of content you have in CollectContent.
  4. Save the integration: Select Save Integration when the flow is ready.

Available blocks

The blocks available for TerminalFour exports include.

  • Within TerminalFour Section: Establishes the section the rest of the flow runs within. This block needs a TerminalFour Section ID.
  • Create TerminalFour Section: Creates a new section in TerminalFour. You can configure the section name, language, status, and whether the section is shown.
  • Create TerminalFour Content: Creates a new piece of content in TerminalFour. You can configure the content type, content name, language, status, and field mappings from CollectContent into TerminalFour elements. If a field is part of a repeatable group, you can use the repeatable-group block to control which repeat instance the mapping should use.
  • For each piece of Content: A block that lets you select which of your CollectContent items should be included in the integration. You can use one or more filters to choose which content is included: Content Name, Folder, Assignees, Workflow Status and Template.
  • For each entry in a repeatable group: A nested helper block for iterating over repeated values.
  • If a field has a specific value: A nested conditional block that only continues when the field matches the value you need.

The flow is nested, so you use these blocks together to build the structure required for the section and content you want to create.

Exported content

Some field types are exported differently:

  • Files from Image and Attachment fields are uploaded to the TerminalFour Media Library, so they can be used in image and file elements in your TerminalFour content type.
  • For Checkbox, radio, and select fields, you can set a listID. If your CollectContent option values match the TerminalFour list item IDs, the values map correctly into TerminalFour lists.

API calls made to TerminalFour

For transparency, the integration makes the following calls to TerminalFour:

  • Fetch content types: GET /contenttype
  • Create a section: POST /hierarchy/{language}
  • Create content: POST /content/{section_id}/{language}
  • Upload media: POST /media

CollectContent sends the TerminalFour API key or authentication token in the Authorization header and requests JSON responses with Accept: application/json.

Run the integration

  1. Save the integration: Select Save Integration.
  2. Run the job: Start the integration job from CollectContent.
  3. Wait for completion: The export runs in the background.
  4. Review the result: Check the job logs for section, content and media creation messages.

If a job fails, review the logs and follow Investigating Failed Integrations. Pleas see Running Integrations for more information.

Good to know

Jobs run in the background, so you can leave this page and come back later to check the job was successful.

Need help?

If you need assistance with this export, contact support.