Skip to main content
Setup time: 2 Min
Connect Notion with All Quiet for streamlined post-incident analysis.

​
Create Outbound Integration

  1. Click on the Outbound Integrations tab.
  2. Click on + Create.
  1. Enter a Display Name for your integration, e.g. “Notion”.
  2. Select a Team.
    For Organizations with Pro and Enterprise plan: This is going to be the root team of your integration. You will be able to add additional teams in the next step.
  3. Select Notion as the integration’s type.
  4. Forwarding settings:
    1. Default: On Forwarding - Notion Pages will only be created if users manually forward specific incidents or if you set up advanced routing rules for your Confluence integration that automatically forward incidents in specific scenarios.
    2. Alternative: On Incident Creation will automatically forward all incidents to Notion as soon as they are created and create new Notion Pages.
      You can change your selection anytime, but we recommend to select On Forwarding. We will explain why in the example below.
  5. Click Create Outbound Integration.

​
Add All Quiet to your Notion Workspace

Once you’ve successfully created your new outbound integration, you’ll automatically be redirected to its Settings page.
  1. Observe that the installation status of the All Quiet integration is still pending.
  2. To complete the integration with your Confluence site, click Add to Notion.
In the Edit tab, you can change general settings like the integration’s Forwarding settings.
Only for Pro and Enterprise plan - Manage your Team Connections: The root team is pre-selected, and you can add the integration to further teams within the root team’s organization. Team Administrators can add / remove those teams they are an Administrator in, Organization Administrators & Organization Owners can manage the connections to all teams of the organization.
You’ll be redirected to Notion, where you’ll have to login first. After login, you you’ll need to select the parts of your Notion Workspace that you want to grant All Quiet permissions to. We request only the permissions essential for All Quiet to operate correctly. These permissions are utilized solely when you interact with the app and are never used for any other purpose.
  1. Click Select pages
  1. Select the pages you want to give All Quiet access to. Note that you can only use these pages as parents for your All Quiet incidents. You can change the selection in your team’s Notion Workspace under Settings > My Connections, anytime.
  2. Click Allow Access.
Next, your are redirected back to your Notion integration’s details page in All Quiet. It’s time to configure the integration. As you can see, the Installation Status changed to installed.
  1. Select the Parent Pages under which you want to create the pages for your All Quiet incidents. You can only select those Notion pages that you granted All Quiet permission to (see prior step).
  2. Make sure to Save Notion Settings after select a parent page, otherwise you cannot forward any incidents.
Notion is now integrated with All Quiet. Depending on your setup, All Quiet incidents can now be forwarded manually to your Notion Workspace or automatically create pages.

​
Creating an Incident Retro Page in Notion

In the following part, we want to quickly demonstrate how a Notion page created from an incident can look like. In the screenshot below, you can find an All Quiet incident.
  1. There was some communication going on, and the team agreed to have a Retro for this incident. That’s why Mads forwarded it to Notion.
  2. The Notion page is linked.
Following the Link to Notion, you will see this:
  1. As defined in my integration’s settings, the page got created below Parent Page “All Quiet CI Integration Tests”
  2. The title of the Notion page is a combination of the timestamp of the incident’s creation and the incident title in All Quiet. Please note that timestamps in the title will always be based on your team’s timezone.
  3. In this section, you will find the main incident details, as well as a link to the incident in All Quiet (see section headline).
  4. This part features all additional incident attributes you previously defined in our mapping engine. Moreover, if there are further links related to the incident, they will be listed here.
  5. All events linked to the incident. Basically the communication in All Quiet.
  6. The team members that were on-call during each event. Only Tier 1 members and members from higher Tiers that got notified due to escalations are listed.
    As the Notion page is a snapshot of the All Quiet incident, we recommend to activate the Trigger On Forwarding feature for your Notion integration. That is because when deciding to automatically create the page with incident creation, there won’t be a lot history / events available.