Integrations

Overview

Integrations let you connect a Strata project to an external issue tracker — Jira, GitHub Issues, or Linear — or to any HTTP endpoint via a Webhook. Once configured, team members can create issues straight from the changelog or from individual entity types without leaving Strata.

Integrations are configured per project. Each project can have multiple integrations of different types (for example, a Jira integration for the client's backlog and a webhook for a CI pipeline). Navigate to your project's Settings → Integrations tab to add, edit, or remove them.

Supported types

Who can manage integrations

Managing integrations (adding, editing, deleting) requires the project:settings permission, which is granted to owners and admins. Members and viewers cannot see integration configuration or credentials.

Creating issues from a configured integration requires the entry:create permission, which is granted to members, admins, and owners. This means any team member who can edit the content architecture can also push issues to connected trackers.

Setting up Jira

To connect Jira Cloud, you need an API token and the details of the Jira project you want to create issues in.

1. Go to your project's Settings → Integrations and click Add Integration.
2. Select Jira as the type and give it a label (e.g. “Client Jira”).
3. Enter the following configuration:
   • Jira URL — your Atlassian instance URL (e.g. https://yourcompany.atlassian.net)
   • Email — the email address associated with the API token
   • API Token — generate one at id.atlassian.com/manage-profile/security/api-tokens
   • Project Key — the Jira project key (e.g. PROJ)
   • Issue Type — defaults to Task, but you can set it to any issue type in your project (e.g. Story, Bug)
4. Click Add Integration to save.

Strata uses Jira's REST API v3 with HTTP Basic authentication (email + API token). The API token is encrypted before storage and never displayed in full after saving.

Setting up GitHub Issues

Connect a GitHub repository to create issues directly from Strata.

1. Click Add Integration and select GitHub Issues.
2. Give it a label (e.g. “Project Repo”).
3. Enter the following configuration:
   • Personal Access Token — a GitHub PAT with the repo scope. You can create one at github.com/settings/tokens.
   • Repository — the repository in owner/repo format (e.g. acme/drupal-site)
4. Click Add Integration to save.

Issues are created via the GitHub REST API. If you configure labels in the integration config, they will be applied to every issue created through this integration.

Setting up Linear

Connect Linear to create issues in your team's backlog.

1. Click Add Integration and select Linear.
2. Give it a label (e.g. “Product Backlog”).
3. Enter the following configuration:
   • API Key — create one at Settings > API in Linear
   • Team ID — the UUID of the Linear team to create issues in
   • Project ID (optional) — if provided, issues will be assigned to this Linear project
4. Click Add Integration to save.

Strata uses Linear's GraphQL API to create issues. If label IDs are configured, they will be applied to every issue created through this integration.

Setting up a Webhook

Webhooks let you send issue-creation events to any HTTP endpoint — a CI pipeline, a Slack bot, a custom dashboard, or any service that accepts JSON payloads.

1. Click Add Integration and select Webhook.
2. Give it a label (e.g. “CI Pipeline”).
3. Enter the following configuration:
   • Webhook URL — the HTTPS endpoint that will receive POST requests
   • Bearer Token (optional) — if provided, sent as an Authorization: Bearer header on every request
4. Click Add Integration to save.

Webhook payload

When an issue is created through a webhook integration, Strata sends a POST request with a JSON body:

{
  "event": "issue.created",
  "title": "Add Tags vocabulary",
  "description": "Optional description text",
  "strata_url": "https://app.usestrata.com/acme/projects/site/..."
}

The strata_url field is included when the issue is created from a specific entity or changelog entry, linking back to that item in Strata. The request always uses Content-Type: application/json.

Creating issues from Strata

Once at least one integration is configured, a Create Issue button appears in two places:

• Changelog — on committed changesets, to create a ticket that references the set of changes
• Entity detail sheet — on individual entity types (content types, vocabularies, media types, etc.), to create a ticket for a specific item

Clicking the button opens a dialog where you can:

1. Select which integration to use (if the project has more than one)
2. Edit the title (pre-filled from the entity name or changeset message)
3. Add an optional description

Strata automatically includes a link back to the originating entity or changeset in the issue body, so your team has context in the tracker. For Jira and Linear, this appears as a clickable link in the issue description. For GitHub, it is appended as a Markdown link.

Editing and removing integrations

Click Configure on any integration card to update its settings. You can change the label, update the configuration (project key, repository, team ID, webhook URL), and rotate credentials.

When updating credentials, leave the field blank to keep the existing credentials. Enter a new value to replace them. The current credentials are shown in a masked format (first and last four characters only).

To remove an integration, click the delete button on its card. This is immediate and permanent — the integration and its encrypted credentials are deleted. Existing issues that were created through it are not affected in the external tracker.

Security

Strata takes several measures to protect your integration credentials:

• Encryption at rest — all credentials (API tokens, personal access tokens, API keys, bearer tokens) are encrypted before being stored in the database. They are decrypted only at the moment an issue is created.
• Masked display — after saving, credentials are never shown in full. The UI displays only a masked version (e.g. ghp_...xYz4).
• Permission-gated access — only users with the project:settings permission (owners and admins) can view integration configuration, including the masked credentials. Members see only the integration type and label when creating issues.
• SSRF protection — webhook URLs and Jira instance URLs are validated before requests are sent, preventing server-side request forgery against internal networks.
• Cascade deletion — when a project is deleted, all of its integrations and encrypted credentials are automatically removed via database cascade.

Related documentation

• Change Tracking — learn about the changelog where issues can be created from committed changesets
• Content Architecture — the entity types and fields that issues can reference
• Team Collaboration — roles, permissions, and who can manage integrations