Skip to main content

Troubleshooting Workflow Emails with Raw Tokens and Integration Sender Addresses (CRM)

This guide helps you resolve issues when workflow emails display raw tokens instead of actual data and appear to be sent from integration addresses like [email protected] or [email protected].

Troubleshooting Workflow Emails with Raw Tokens and Integration Sender Addresses

Common Symptoms

  • Emails show raw tokens (like {{token_name}}) instead of actual patient or record data

  • Emails appear to be sent from integration addresses such as [email protected] or [email protected]

  • Multiple duplicate emails are being sent for the same records

  • Email content appears incomplete or incorrectly formatted

Root Causes

Token Display Issues

Raw tokens appear when workflow tokens are not correctly mapped to the appropriate module fields or when the workflow triggers without proper data context.

Integration Sender Addresses

Emails appear to come from integration addresses because workflows use the 'Assigned To' user's email as the sender by default. When records are automatically assigned to integration users (CTM, TalkFurther), their email addresses become the sender.

Excessive Email Sending

Workflows configured to trigger 'Every time conditions are met' will send emails repeatedly whenever records are updated, causing duplicates.

Solution Steps

Step 1: Fix Token Mapping

  1. Navigate to your workflow settings and locate the email template

  2. Review all tokens used in the email body and subject line

  3. Ensure tokens are correctly mapped to the right module fields (e.g., Intake Opportunity fields)

  4. Test the token mapping by previewing the email with actual record data

Step 2: Update Workflow Trigger Logic

  1. Open the workflow configuration

  2. Change the trigger setting from 'Every time conditions are met' to 'Only first time conditions are met'

  3. This ensures emails are sent only once per record when conditions are initially satisfied

  4. Save the workflow settings

Step 3: Correct Sender Email Address

  1. In the workflow email settings, locate the 'From' address configuration

  2. Change from 'Assigned To' user email to system default email ([email protected])

  3. This prevents emails from appearing to come from integration addresses

  4. Save the changes

Step 4: Test the Workflow

  1. Create a test record that meets the workflow conditions

  2. Verify the email is sent with properly populated data instead of raw tokens

  3. Confirm the sender address appears as intended

  4. Monitor for 24-48 hours to ensure no duplicate emails are sent

Expected Results

After implementing these fixes, you should see:

  • Emails display actual data instead of raw tokens

  • Sender address shows as system default rather than integration addresses

  • Only one email sent per record that meets the workflow criteria

  • Properly formatted email content with complete information

⚠️ Important Notes

  • Review all active workflows in your system, as multiple workflows may have similar configuration issues

  • When workflows are assigned to integration users (CTM, TalkFurther), the sender will default to those addresses unless specifically changed

  • Always test workflow changes before deploying to avoid unintended emails to clients

When to Contact Support

Contact Dazos Support if:

  • Token mapping issues persist after following the troubleshooting steps

  • You discover multiple workflows with similar configuration problems

  • Emails continue to display raw tokens despite correct field mapping

  • You need assistance identifying which specific workflows are causing issues

  • The problem affects multiple treatment programs or locations

Related Resources

  • How to Fix Workflows Sending Excessive Emails and Texts

  • Workflow Email Token Configuration guides

  • Email Notification Settings documentation

Did this answer your question?