Messaging and record actions are the steps in an Automation Workflow that send emails, create tasks, change records and send data to other systems in Prospect CRM. You need to be a CRM Admin, and the workflow must be open in edit mode. To add a step, see Use the workflow builder.
Send Email
The Send Email step sends an email to customers or colleagues. Choose a Content Source to decide whether to use a template or write the email in the step.
Use template
Set up these fields:
Email Template (required): The document template to send. The template's attachments and signature are included automatically.
To: Who to send to. Leave blank to send to the triggering record's Contact.
From Address and From Name: Optional. Leave blank to use the template's settings, shown as greyed-out placeholders.

Write from scratch
Set up these fields:
From Address and From Name: Optional. Who the email appears to come from.
To: Who to send to. Leave blank to send to the triggering record's Contact.
CC: Optional. Anyone who should get a copy of the email.
BCC: Optional. Anyone who should get a copy without the other recipients seeing their address.
Subject (required): The email's subject line.
Signature: Optional. The email signature to add at the end of the email, or None.
Body: The content of the email.

Who receives the email
If you fill in the To field, the email goes to those addresses. If To is blank, it's sent to the triggering record's Contact. For a Contact Created workflow, it's sent to the Contact themselves. If there's no valid address, the step fails with 'Record does not have a parent with a valid email address.'
You can use merge fields in the address, subject and body fields, for example to address the email to the account manager or include the Opportunity name. Sent emails are saved as documents against the record, as with emails sent manually. For details, see Use merge fields.
Create Task
The Create Task step creates a CRM task against the triggering record. Set up these fields:
Name: The task subject.
Assigned To: The user who should get the task. You can choose a specific user or use a merge field, such as the record's account manager or the result of a Select Value step.
Due Date: When the task is due. Choose Fixed Date for a specific date, or Dynamic Date to set the Number of days after the task is created. You can also pick a date field from the triggering record.
Description: More detail for the user. Type @ to mention and notify users.

The task is linked to the triggering record and its related Company, Contact and Opportunity where applicable. If the triggering record type doesn't support tasks directly, the task is linked to the closest related record.
Add Tag and Remove Tag
The Add Tag and Remove Tag steps add tags to, or remove tags from, a record. This is useful for segmentation, reporting and marketing lists.
Click Select Target, then choose which record to tag. This can be the triggering record or a related record, for example the Company or Contact of an Opportunity.
Choose the tags to add or remove.
đNote: Remove Tag only removes tags that are present. It doesn't fail if the record doesn't have the tag.
â ď¸Important: If you add an Add Tag or Remove Tag step but don't choose a tag, the workflow carries on past that step without adding or removing anything. The step doesn't show a Needs setup label.
Update fields
The Update fields step updates fields on the triggering record automatically. For example, you can set an Opportunity's Stage to 'Follow up required' after a chaser has been sent.
Click Add Field, then pick the field to update. Only fields that can be edited are listed, including your custom fields.
Enter the new value in the Value field. You can use merge fields, for example to copy a value from another field or a step output.
Add as many fields as you need.
Fire Webhook
The Fire Webhook step sends data to an external system, such as Zapier, Power Automate or your own service, so processing can continue elsewhere. Set up these fields:
Webhook URL (required): The address to send to.
Request Body: The JSON to send. Use merge fields to include record data.
Username and Password: Optional Basic Authentication credentials.
