Notifications

Learn how to manage your email notifications in your Fivetran dashboard.

Overview

In Fivetran, a notification is an automatically-generated email. It quickly informs you about important activity in your Fivetran account, like connector failures and any other types of errors, so that you can resolve any potential issues as soon as possible. You can customize notification settings on the Notifications page to only receive the notifications that you want.

NOTE: Your notification settings are unique to your user, so changing them does not affect the settings for other users on your shared account.

There are three categories of notifications:

• Connector notifications
• Transformation notifications
• Account notifications

Disable all notifications

Notifications are enabled in your account by default to inform you about your account's activity. If you don't want to receive any notifications, you can disable them by setting the toggle in the top right corner of the Notifications page to OFF.

Check notification email

We send notifications to the email address that you use to log in to your Fivetran dashboard. You can see this email address at the top of the page.

Connector notifications

Manage notifications about your connectors on the Connectors tab. We send you notifications in the following situations:

NOTE: Which connector notifications you receive depends on your user role and connector type. (We do not send New Data Detected notification emails for connectors that don't support data blocking or column hashing due to limitations in how we track schema changes.)

• MAR estimate available: During a connector's free use period, we notify all users who subscribe to that connector when its MAR and usage estimate is ready. Learn more in our MAR and usage estimate documentation.

• Connector trial ended: We notify all users who subscribe to a connector when its 14-day free use period ends. Learn more in our New connector free use period documentation.

• New error: If your connector breaks and we know the problem and potential resolution steps, we generate an Error in your dashboard that tells you how to resolve the problem. We then send you a notification with details about the Error and what you need to do to resolve that Error.

  NOTE: If your connector needs to be reconnected, we send an Error notification after the second sync failure because the first failure is often caused by transient connection issues. If the destination associated with your connector needs to be reconnected, we send one Error notification per destination after the first sync failure.

• Failed syncs: If your connector breaks, and we do not know why, we do not generate an Error in your dashboard. Instead, we send you a notification about the broken connector after three failed syncs in a row. After a connector is broken without an Error for 48 hours, Fivetran automatically escalates the issue to our support and engineering teams. Our team may email you to troubleshoot the issue. Since these emails are generated in our support portal, your notification preferences do not apply to them.

• New source data (optional): If you subscribed to schema change notifications, we send you a notification when we detect a new data object in the source. Learn more in our Schema Change settings documentation.

• Sync delays: If your connector is enrolled in delay notifications, we send you a notification when your connector's sync is delayed. When determining whether a connector is delayed, we consider the average duration of its syncs over a rolling 14-day period, its sync frequency, and your specified delay notification setting.

  Sync delays can be caused by a variety of reasons, such as a larger-than-usual data set to sync or the connector reaching the source API rate limit. We also send you a notification when the connector's sync delay ends, which means the sync successfully completed.

  NOTE: You can control a connector's sync delay notification settings on its Setup tab. When you change the delay notification setting while your connector has notifications disabled, you will be prompted to Activate the notifcations.

In the Active Notification Subscriptions section, you'll see a list of all connectors that you currently receive notifications for. You can search for a connector using the search bar or filter the list by source and/or destination.

Add notifications

To add notifications for a connector, click the + Add button.

The Add a notification subscription window lists the transformations that you have access to but that you do not currently receive notifications for. You can search for a transformation using the search bar or filter the list by destination. You can select multiple transformations at once. Once you've selected the transformation(s) you want to receive notifications for, click Apply changes.

Remove notifications

To remove notifications for a connector, select the checkbox next to the connector, then click Remove selected.

Manage notification settings

To manage your notification auto-subscription settings, click the gear icon.

A drop-down menu opens showing your auto-subscription options. Choose one of the following auto-subscription options based on your notification preferences:

N0TE: Changes to your auto-subscription settings are not retroactive. By default, new users are not subscribed to existing connectors to avoid cluttering your inbox. For example, if you choose to receive notifications for all new connectors on June 1, you won't be subscribed to notifications for a connector created on May 31. If you want to receive notifications for existing connectors, add notifications for your chosen connectors.

You can also enable or disable alert reminder emails. These emails, whose subject lines always begin with "Reminder:", notify you when your connector has an unresolved Error or delay.

NOTE: By default, alert reminder emails are disabled to avoid cluttering your inbox.

You can use the clean up tool to retroactively apply your auto-subscription settings to the connectors that have different notification subscriptions. For example, if your auto-subscription setting is "Only connectors that I create" and you're currently subscribed to a connector you didn't create, that subscription would be removed. Similarly, if you weren't subscribed to a connector that you created, then a subscription would be added for that connector.

To clean up your auto-subscription settings, do the following:

1. At the top of the auto-subscription drop-down menu, click Clean up.
2. In the Subscription cleanup window, review the list of connectors that don't have your current auto-subscription settings.
3. Click Apply changes to update their settings.

Transformation notifications

Manage notifications about your transformations for dbt Core* on the Transformations tab. If your transformation fails, we generate an Error in your dashboard that tells you how to resolve the problem and send you a notification with details about that Error.

In the Active Notification Subscriptions section, you'll see a list of all transformations that you currently receive notifications for. You can search for a transformation using the search bar or filter the list by destination.

Add notifications

To add notifications for a transformation, click the + Add button.

The Add a notification subscription window lists the transformations that you have access to but that you do not currently receive notifications for. You can search for a transformation using the search bar or filter the list by destination. You can select multiple transformations at once. Once you've selected the transformation(s) you want to receive notifications for, click Apply changes.

Remove notifications

To remove notifications for a connector, select the checkbox next to the connector, then click Remove selected.

Manage notification settings

To manage your notification auto-subscription settings, click the gear icon.

A drop-down menu opens showing your auto-subscription options. Choose one of the following auto-subscription options based on your notification preferences:

N0TE: Changes to your auto-subscription settings are not retroactive. By default, users are not subscribed to existing transformations to avoid cluttering your inbox. For example, if you choose to receive notifications for all new transformations on June 1, you won't be subscribed to notifications for a transformation created on May 31. If you want to receive notifications for existing transformations, add notifications for your chosen transformations.

You can use the clean up tool to retroactively apply your auto-subscription settings to the transformations that have different notification subscriptions. To clean up your auto-subscription settings, do the following:

1. At the top of the drop-down menu, click Clean up.
2. In the Subscription cleanup window, review the list of transformations that don't have your current auto-subscription settings.
3. Click Apply changes to update their settings.

Account notifications

Manage notifications about your account activities on the Account tab.

NOTE: The Account notifications page looks different based on your user permissions and which deployment models you use.

Use the toggles to enable or disable the following account notifications:

• Monthly spend warning: Receive a notification when you exceed your monthly spend threshold. You can change this threshold on the Billing tab. You need an Account Administrator or Account Billing role to receive this notification.
• Low spend warning (enabled by default): Receive a notification 45 days before your spend balance runs out. You need an Account Administrator or Account Billing role to receive this notification.
• System Outages (enabled by default): Receive a notification when there is a general Fivetran user interface outage. System outage notifications don't include incidents related to specific components, such as individual connectors or destinations. In addition, you can't subscribe non-Fivetran users to these notifications on the Account tab. However, you can enable notifications for specific components and subscribe non-Fivetran users to receive outage notifications on the Fivetran Status Page. See How Can I Subscribe to Fivetran Status Updates? to learn more.
• Failed Webhooks (if you have webhooks set up): Receive a notification when webhook events fail to be sent.
• HVR table refresh (if you use the HVR self-hosted deployment model): Receive a reminder that HVR refreshes count toward paid usage after the troubleshooting window following the first table refresh each month.

Manage other users' notifications

IMPORTANT: This feature is only available for users with an Account Administrator or a custom role that has permissions to manage users and view connectors and transformations. Learn more about user roles in our role-based access control documentation.

To edit the notification settings for other users on your account, click the Switch Recipient link on the top of the Notifications page:

A modal with a user email list appears. Click the email address of your chosen user or create a new recipient in the Enter new email recipient field:

The notification settings for your chosen user appear. Edit their settings in the usual way.

To go back to your own notification settings, click Back to your notifications.

Send notifications to any email address

Do the following to send Fivetran notitfications to any email address:

1. At the top of the Notifications page, click Switch Recipient.

2. A pop-up window with a user email list appears. Enter the email address of the non-Fivetran user, then click Create. You'll be redirected to the new user's notifications settings.

   

3. By default, the new user has no notifications. Click Add to subscribe the user to notifications.

4. If you want to delete the non-Fivetran user, click the trash can icon next to the user name.

5. A pop-up message appears. Read it, then click Delete recipient.

Send notifications to third-party systems

You can set up your Fivetran notifications to send to the following third-party systems (among others):

• Slack
• Microsoft Teams
• Opsgenie
• PagerDuty
• ServiceNow

Follow the instructions for your system below.

Slack

NOTE: Creating a channel email address is the simplest way to send Fivetran notifications to Slack. Learn about other methods in Slack's Send emails to Slack documentation.

1. In Slack, go to the channel that you want to send Fivetran notifications to.
2. Follow Slack's Create an email address for a channel or DM instructions to create an email address for the channel.
3. Follow our Send notifications to any email address instructions to send notifications to this email address.

Microsoft Teams

1. In Teams, go to the channel that you want to send Fivetran notifications to.
2. Follow Microsoft's Send an email to a channel instructions to find the channel email address.
3. Follow our Send notifications to any email address instructions to send notifications to this email address.

Opsgenie

1. Follow Opsgenie's Integrate your email with Opsgenie instructions to create an email address for your Fivetran notifications.
2. Follow our Send notifications to any email address instructions to send notifications to this email address.

PagerDuty

1. Follow PagerDuty's Email Integration Guide to create an email address for your Fivetran notifications.
2. Follow our Send notifications to any email address instructions to send notifications to this email address.

ServiceNow

1. In ServiceNow, go to the channel that you want to send Fivetran notifications to.

   NOTE: The channel type must be Email.

2. Follow ServiceNow's Create a flow with an inbound email trigger instructions to find the channel email address.
3. Follow our Send notifications to any email address instructions to send notifications to this email address.

* dbt Core is a trademark of dbt Labs, Inc. All rights therein are reserved to dbt Labs, Inc. Fivetran Transformations is not a product or service of or endorsed by dbt Labs, Inc.