Customer support |
Login |

Integrations

Regulatory compliance inside your tools. Not the other way around.

An action becomes a ServiceNow or Jira ticket, a Slack message, a Teams card, a deadline in Outlook or Google Calendar. Connections are outbound and encrypted: your IT team chooses what goes out, and every send is logged.

Swipe to see the full screen

The tools' real logos: an action goes out to each of them.

What changes

Your week, without and with Obsidian.

Before

Everything goes through emailAlert to forwardCopy-paste into JiraFW: new ruleTasks.xlsxMissed deadlineRetyped in ServiceNowWho is handling it?ReminderSent?

Without Obsidian

  • Alerts stuck in an inbox
  • Tasks retyped by hand into Jira or ServiceNow
  • Deadlines missing from calendars

After

0 retyping
ServiceNow ticket createdAssigned to S. de VosDeadline added to the calendar10 November 2026

With Obsidian

  • Every action sent to the team's own tool
  • The ticket created and tracked, with no retyping
  • Deadlines in Outlook or Google Calendar

The benefits

What you gain, in concrete terms.

An action goes out to your tools

01Connectors

Your tools, as they are

ServiceNow, Jira, Slack, Teams, Outlook, Google Calendar: your teams stay where they work.

Ready-to-use connectors
Created by Obsidian

Align the 2026 sustainability statement with the revised ESRS

Assigned to S. de VosDeadline 10 Nov 2026

02Tickets

No more retyping

The action lands in the tool with its owner and its deadline. Nobody copies anything.

Ticket creation
Outbound connections only
End-to-end encrypted
Every send logged
Your IT team chooses what goes out

03Security

Your IT team stays in control

Outbound, encrypted connections, every send logged: your IT team decides what goes out.

Connection security

In your industry

A real case, step by step.

Pick your industry: the example follows, with a real official publication and the fictional Meridian group.

Examples for:
Council of the European Union29 June 2026

Digital omnibus on AI: final green light from the Council

Effective date
  1. The actionClassify the applicant screening tool against Annex III

    For Meridian Netherlands B.V.

  2. The sendServiceNow ticket created, Slack message to the team

    No retyping, send logged.

  3. The follow-upDeadline: 28 November 2026

    In Sanne de Vos's calendar.

FDAFDA2 February 2026

Medical devices: the FDA's QMSR takes effect

Effective date
  1. The actionTrain the US team on the transition to the QMSR

    For Meridian America Inc.

  2. The sendServiceNow ticket created, Slack message to the team

    No retyping, send logged.

  3. The follow-upDeadline: 13 November 2026

    In David Brenner's calendar.

EPAEPA14 October 2026

Trichloroethylene: the EPA proposes to extend certain compliance dates

Deadline
  1. The actionReview the TCE phase-out plan against the dates proposed by the EPA

    For Meridian America Inc.

  2. The sendServiceNow ticket created, Slack message to the team

    No retyping, send logged.

  3. The follow-upDeadline: 30 November 2026

    In David Brenner's calendar.

European CommissionEuropean Commission21 September 2026

ESRS: revised Set 1 published in the Official Journal

Effective date
  1. The actionAlign the 2026 sustainability statement with the revised ESRS

    For Meridian Netherlands B.V.

  2. The sendServiceNow ticket created, Slack message to the team

    No retyping, send logged.

  3. The follow-upDeadline: 10 November 2026

    In Sanne de Vos's calendar.

SECSEC21 September 2026

Proxy rules: the SEC proposes to modernize its rules and repeal Rule 14a-8

Consultation
  1. The actionDecide on a comment letter to the SEC

    For Meridian America Inc.

  2. The sendServiceNow ticket created, Slack message to the team

    No retyping, send logged.

  3. The follow-upDeadline: 20 November 2026

    In David Brenner's calendar.

CFTCCFTC13 October 2026

Crypto assets: the CFTC publishes an advance notice on two future rules

Consultation
  1. The actionAssess the CFTC advance notice on crypto asset markets

    For Meridian America Inc.

  2. The sendServiceNow ticket created, Slack message to the team

    No retyping, send logged.

  3. The follow-upDeadline: 14 December 2026

    In David Brenner's calendar.

How it works

The result: your tools connected, in a few clicks.

1The Integrations page

Every connector, its status and its last send.

Real app screen.

Frequently asked questions

Your questions, our answers.

Obsidian Integrations send each compliance action to the tools teams already use (ServiceNow, Jira, Slack, Microsoft Teams, Outlook, Google Calendar) over outbound, encrypted and logged connections.

Which tools?

ServiceNow, Jira, Slack, Microsoft Teams, Outlook and Google Calendar, plus a signed webhook, an API and the MCP server.

What leaves Obsidian?

Whatever your IT team allows: connections are outbound and encrypted, and every send is logged.

Do I need any development?

No: every connection is configured from the Integrations page.

What about single sign-on?

Yes, with Microsoft Entra ID.

Obsidian Regulatory Intelligence

See it on your own regulatory perimeter

Start your free trial: our team configures a workspace on your own regulatory perimeter within 1 to 2 business days and walks you through it.