How to Use the Send Email Workflow Action in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

The Send Email workflow action sends automated, personalized emails when a workflow reaches the step. Configure sender details, subject, body (with merge fields), optional attachments, CC/BCC, and run a test before saving.

The Send Email action triggers an automated email when a Sparkforge workflow reaches the step. Use it for booking confirmations, reminders, follow-ups, and promotional sends — anything where timing and personalization matter.

Why it is useful

  • Timely — emails go out the moment the workflow says so.
  • Personalized — merge fields like first name, appointment time, and custom values.
  • Consistent — templates keep tone and design the same across the team.
  • Hands-off — no one has to remember to send the message.
  • Flexible — attachments, custom HTML, CC/BCC.

Configure the Send Email action

1. Add the action

Open the workflow editor and drop the Send Email action where it should fire — usually right after a trigger like an appointment booking or form submission.

2. Name the action

Use something specific (for example, Booking Confirmation Email). Specific names matter when a workflow has 20 steps.

3. Sender details

  • From Name — the name recipients see (for example, your business name).
  • From Email — the address the email sends from. Use a domain you have verified.

4. Subject line

Short, specific, and signal-rich. Thanks for booking with us! beats Confirmation.

5. Body and templates

Pick a template from the dropdown or write a custom email. Use merge fields for personalization:

Hi {{contact.first_name}}, thanks for booking. Your appointment is at {{appointment.start_time}}.

If you select an existing template, you may see a Sync Edits to Template checkbox. When sync is on, edits in the workflow email and the original template update each other. When off, they stay independent.

6. Attachments (optional)

Attach files like booking confirmations, product details, or invoices.

7. Test the email

Enter an address in the Test Emails field and click Send Test Mail. Check formatting, merge fields, and links across at least one inbox.

8. Save and activate

Click Save Action. The email fires automatically when the workflow hits this step.

9. CC and BCC

Click the cc or bcc buttons to expose those fields, then add addresses comma-separated.

Example: booking confirmation email

Goal: send an email when a contact books an appointment.

  • Trigger: Appointment booked.
  • Action: Send Email.
  • Action Name: Booking Confirmation Email.
  • From Name: your business name.
  • Subject: Thanks for booking with us!
  • Body: Hi {{contact.first_name}}, thanks for booking. Your appointment is at {{appointment.start_time}} on {{appointment.only_start_date}}.
  • Optional: attach an appointment details PDF.
  • Send a test, then save.

Troubleshooting

  • Email did not send — confirm the contact has a valid email and the sender domain is set up.
  • Merge fields blank — the trigger or contact record has no value for that field. Appointment fields require an appointment-related trigger.
  • Formatting looks off — test across email clients and tighten templates.

Best practices

  • Short, specific subject lines.
  • Use templates for consistency.
  • Personalize with merge fields, but only fields that exist for every trigger.
  • Comma-separate CC/BCC addresses carefully.

Frequently Asked Questions

Can I use templates with the Send Email action?
Yes. Pick an existing template from the dropdown or write a custom email directly in the editor.
Do CC and BCC recipients show up in workflow email stats?
No. Only the primary contact's send is counted in Email Stats. Workflow success is determined by delivery to the primary contact.
Does Send Test Mail validate CC and BCC delivery?
No. Test emails check formatting and content only. They do not confirm CC or BCC delivery.
What happens if a CC or BCC address is invalid?
Invalid CC/BCC addresses are skipped. The primary contact and any valid CC/BCC recipients still get the email.
Why are merge fields blank in my email?
Merge fields go blank when the trigger context does not provide that data (for example, appointment fields require an appointment trigger) or the contact record is missing values.
Why did my email land in spam?
Deliverability comes down to sender setup and domain configuration. Verify SPF, DKIM, and DMARC, and test with multiple inbox providers.

Was this article helpful?