Directus

Overview

The Directus destination connector lets you authenticate to a Directus instance using an API token.

This destination is currently in development. Credentials can be validated, but loading data into Directus is not yet supported.

Setup

1. Identify your Directus instance URL (for example, https://directus.example.com).
2. Create an API token in Directus:
   • In the Directus Admin App, create a token for a user/role with the permissions you intend to use for writing data.
3. Copy the token value for use in the connector configuration.

Authentication

This connector authenticates using a Bearer API token.

During credential validation, the connector calls:

• GET /server/info

and expects a successful response when the token and URL are valid.

Configuration

Field	Type	Required	Description
url	string	✅	Base URL of your Directus instance. Must be an HTTPS URL with a host. If you provide a host without a scheme (for example directus.example.com), the connector will assume https://.
api_token	string	✅	Directus API token used as a Bearer token for authentication.

URL requirements

• The URL must use https://.
• Trailing slashes are allowed (they will be handled automatically).

Examples:

• ✅ https://directus.example.com
• ✅ directus.example.com (treated as https://directus.example.com)
• ❌ http://directus.example.com (HTTP is not allowed)

Data loading support

Data loading is not yet implemented for this destination. Runs will fail with an error indicating that Directus destination loading is still in development.

Streams

Not applicable (destination connector).