Integrations
Dastra integrates with Zapier automation platform and many other tools
Integrations
Dastra connects to the tools your teams already use: import your application inventory from your ITAM or CMDB, synchronize data subject requests with your ticketing tool, post notifications in your collaboration channels, stream your security audit logs to your SIEM, or attach files from your cloud drives. Native connectors cover the most common tools; Zapier covers everything else.
The integration store is available in Settings > Integrations of your workspace. It lists every available integration, filterable by category and by the Dastra object it targets, with an All / Installed switch.
How native integrations work
Every native integration is built on three concepts:
Use cases — each integration exposes one or more use cases (for example import applications as assets or synchronize data subject requests). Use cases are installed, enabled, configured and uninstalled independently.
Connections — a connection stores how Dastra authenticates against the external tool: credentials stored encrypted by Dastra, or a delegated OAuth authorization. You can create several connections to the same tool (a production and a sandbox instance, for instance) and choose which one each use case relies on. Connections display their health and can be tested at any time.
Field mapping — import use cases let you choose, for each Dastra field, the external field that fills it, with default values, value transcoding for closed lists (statuses, lifecycle stages…) and AI-assisted suggestions.
Import connectors synchronize once a day and on demand with Run synchronization now. Every execution is traced in the integration logs, with the number of created, updated, flagged and in-error items.

Read the details in Connections, use cases and field mapping.
Available integrations
ServiceNow
Imports the business applications of your CMDB as assets and keeps them in sync daily
Jira
Creates and tracks data subject requests from your Jira project, and transitions the linked issues as requests move through their workflow
Slack
Delivers Dastra notifications in your Slack workspace
—
OneDrive / Google Drive
Attaches files from your drives to your actors, security measures, processing activities, tasks, incidents…
Incoming mail
Turns the emails sent to a dedicated collection address into tasks, requests, data breaches, contracts or processing activities
SIRENE (INSEE)
Fills in your stakeholders' details from the French company registry
—
AI provider
Connects any OpenAI-compatible AI provider to the Dastra assistant
—
Zapier
Connects Dastra to more than 3,000 applications through automated workflows
Some integrations apply to your whole organization rather than to a workspace — single sign-on, SIEM streaming, Office 365 / Gmail and the AI provider. Their tile in the store takes you to the corresponding organization settings, where they are configured by an account owner.
Zapier: connect everything else
Zapier is an online automation tool that connects your applications and services without code. A Zap is an automated workflow made of a trigger and one or more actions: when the trigger event occurs, the actions run.
On the Dastra side, Zapier can react to two triggers — new data subject request created and new task created — and perform six actions: create a task, create an actor, create a data subject request, link an actor to an existing processing activity, search an actor, and find or create an actor. You can therefore start from a Dastra event to act in a third-party application, or start from a third-party event to act in Dastra.
Pre-configured templates (Salesforce, Zoho, Trello, Google Sheets, Excel, Outlook, Azure DevOps…) are available from the Dastra page of the Zapier catalog, and the Zap editor lets you build your own workflow from scratch. See Integrating Dastra with external tools and the Zapier FAQ.
Security and data protection
Integration credentials and tokens are stored encrypted, are never returned by the API, and are erased when you uninstall an integration or delete a workspace.
OAuth flows strictly validate their callbacks, and the inbound webhook endpoints are rate-limited.
Integrations are scoped to a workspace: data from one workspace is never visible from another.
Records created by an integration (assets, requests…) belong to your workspace and are kept when the integration is uninstalled.
Need something else?
If no integration matches your need, the Dastra REST API lets you build your own scripts and connectors, and you can submit a connector request to the Dastra team through the support.
Last updated
Was this helpful?