Failure Notifications
Pipedrive Utilities can send email notifications when background operations fail. This ensures your team is aware of issues that would otherwise go unnoticed since webhook handlers and cron jobs run without a user session.
Email Configuration
All notification settings are in Settings > General under the Failure Notifications section.
| Field | Description |
|---|---|
| SMTP2GO API Key | Your SMTP2GO API key for sending transactional email. |
| From Address | The sender email address. Use the Load Senders button to fetch verified domains and single senders from SMTP2GO, then select one. |
| Display Name | The friendly name that appears in the “From” field (e.g., “Pipedrive Utilities”). |
| Notify Addresses | Comma-separated list of email addresses that will receive failure alerts. |
The Load Senders button queries the SMTP2GO API to retrieve your verified sender domains and individual sender addresses. Only addresses from verified domains or explicitly verified single senders can be used as the “From” address.
Notification Categories
Each category corresponds to a specific failure scenario. Enable or disable categories individually using the checkboxes in the General settings pane.
| Category | Description |
|---|---|
automation_user_not_configured |
A webhook fired but no automation user has been designated. Non-interactive API calls cannot proceed. |
automation_user_token_expired |
The automation user’s OAuth token has expired and the refresh attempt failed. Re-authentication is required. |
gads_group_not_found |
An inbound Google Ads webhook referenced a conversion group UUID that does not exist in the database. |
gads_gclid_missing |
A Google Ads conversion was triggered for a deal that has no GCLID value in the configured custom field. |
gads_token_refresh_failed |
The Google Ads OAuth token could not be refreshed. Re-authentication through the Google Ads OAuth flow is required. |
gads_upload_failed |
The Google Ads API rejected the conversion upload request. The error details are included in the notification body. |
panel_config_sync_failed |
Panel → n8n config sync failed after retries. |
mc_api_unreachable |
Mailchimp API unreachable during save/validation. |
The gads_group_not_found category cannot currently trigger an email notification because the company ID is unknown at that point in the webhook request – the conversion group UUID is the only identifier available. The category exists in the registry for future use if a company lookup strategy is added.
How Notifications Work
When a failure occurs in the worker, the code calls sendNotification(settingsStore, companyId, category, subject, body). This function:
- Checks whether the company has SMTP2GO credentials configured.
- Checks whether the specific category is enabled (subscribed).
- If both conditions are met, sends an email via the SMTP2GO HTTP API.
- The function never throws – notification failures are logged but do not interrupt the main operation.