---
title: "Preventing Workflow Automation email notifications from being blocked"
canonical_url: "https://www.nutrient.io/guides/workflow-automation/troubleshooting/why-are-notifications-from-our-cloud-instance-being-dropped-blocked-or-marked-as-spam/"
md_url: "https://www.nutrient.io/guides/workflow-automation/troubleshooting/why-are-notifications-from-our-cloud-instance-being-dropped-blocked-or-marked-as-spam.md"
last_updated: "2026-05-15T19:10:05.124Z"
description: "Learn how to prevent email notifications from Nutrient Workflow Automation Platform from being blocked or marked as spam by email servers."
---

# Preventing email notifications from being blocked

Email notifications from Nutrient Workflow Automation Platform can sometimes be blocked, dropped, or marked as spam by email servers. This guide helps admins troubleshoot and prevent these delivery issues to ensure reliable communication.

## Server information

For Nutrient Workflow Automation Platform Trials, Shared Cloud, and Private Cloud accounts:

**Fully qualified domain name:** `cloudmail.integrify.com`\

**IP Address:** `52.44.253.12`

## Common solutions

Below are common methods to prevent email notifications from being blocked or marked as spam.

### Enable Nutrient’s cloud email server

Configure your email server to enable communications from our server to bypass spam and virus filtering algorithms. If your organization receives many notifications from Nutrient Workflow Automation Platform, this approach also reduces CPU usage on your mail server.

### Allowlist your system email address

If you can’t configure server-wide email enabling, add the specific email address used for sending notifications in Nutrient Workflow Automation Platform to your server’s global allowlist.

### Configure SPF records

Nutrient Workflow Automation Platform already has valid SPF and PTR records for our cloud server. You only need to modify your DNS SPF record if you’re using a system email address from a domain other than `integrify.com`.

**When SPF configuration is needed:**

- Your Nutrient Workflow Automation Platform instance uses a system email address like `notification@mydomain.com`

- Your personal email is `me@mydomain.com`

- Your email server performs reverse DNS and SPF record validation

Without proper SPF records containing either `ip4:52.44.253.12` or `include:integrify.com`, email delivery may fail.

#### Adding our server to your SPF record

1. Access your DNS management console

2. Locate your domain’s SPF record (a TXT record starting with `v=spf1`)

3. Add either `ip4:52.44.253.12` or `include:integrify.com` to your existing SPF record

4. Save changes and allow time for DNS propagation

**Example SPF record:**

```

v=spf1 include:integrify.com ~all

```

## Additional resources

For detailed SPF record syntax information, refer to the [SPF Record Syntax documentation](http://www.open-spf.org/SPF_Record_Syntax/).

## Next steps

After implementing these changes:

1. Test email delivery by triggering a notification from your Nutrient Workflow Automation Platform instance

2. Monitor your email server logs for any remaining delivery issues

3. Contact [Nutrient support](https://support.nutrient.io/hc/en-us/requests/new) if problems persist after implementing these solutions
---

## Related pages

- [Improve your PDF exports with streamlined forms](/guides/workflow-automation/troubleshooting/when-i-export-to-pdf-some-fields-are-blank-even-though-the-formatted-view-shows-those-boxes-as-completed.md)
- [Optimize your notification settings for Workflow Automation](/guides/workflow-automation/troubleshooting/error-in-the-custom-notification-for-this-email-please-notify-the-process-owner.md)
- [Understanding notifications in Workflow Automation](/guides/workflow-automation/troubleshooting/when-i-change-my-process-to-a-testing-or-production-publish-status-some-notifications-are-not-being-sent-to-task-recipients.md)
- [My request won’t flow to the next task](/guides/workflow-automation/troubleshooting/my-request-wont-flow-to-the-next-task.md)
- [Streamline task assignments with upcoming features](/guides/workflow-automation/troubleshooting/integrify-will-not-allow-me-to-assign-a-whole-group-to-an-initialized-task.md)
- [Ensure seamless command execution in automation](/guides/workflow-automation/troubleshooting/when-i-run-a-command-directly-on-the-server-it-works-fine-however-when-run-from-the-command-line-task-type-it-fails.md)
- [Configure your email server for scheduled reports](/guides/workflow-automation/troubleshooting/why-am-i-not-receiving-scheduled-reports.md)