Automations
Actions

Actions

An action is the task that Gordon CRM executes automatically when a trigger event fires.

Gordon CRM supports seven action types, grouped into five operational areas.

Tag Actions

Tag actions adjust a contact's tags. These are managed on the central Automations page (/automations).

1. Add Tag

Adds the selected tag to the contact.

  • Chaining (Cascading): Applying a tag fires a tag_applied trigger. This allows you to chain rules together (e.g., submitting a form adds a "Lead" tag, which then triggers a second rule to enroll them in a campaign).
  • Safe Execution: If the contact already has the tag, the system does not re-apply it and does not fire duplicate cascading triggers.

2. Remove Tag

Removes the selected tag from the contact.

  • Cascading: Removing a tag fires a tag_removed trigger, which can trigger exit workflows. If the contact doesn't have the tag, the operation is skipped.

Campaign Actions

Campaign actions control contact progress through automated email sequences. These are managed directly on the Campaign detail page to keep sequence logic together.

3. Enroll in Campaign

Enrolls the contact in the selected email campaign. The system runs several safety checks first:

  • No Duplicates: Contacts cannot be enrolled in the same campaign more than once at the same time.
  • Status Gating: You cannot enroll contacts in draft or paused campaigns.
  • Late Enrollee Check: If a campaign step is date-based and the date has already passed, the system skips it. If all steps are in the past, the enrollment is marked complete immediately.

4. Remove from Campaign

Unenrolls the contact from the selected campaign, canceling any scheduled emails. This is useful for stopping campaigns when a contact takes action (e.g., removing a contact from a nurture campaign once they are tagged as "Customer").

Task Actions

Task actions create action items for your team.

5. Create Task

Automatically creates a to-do task.

  • Inline Setup: Since the task is created dynamically, you fill in a blueprint form when creating the rule:
    • Task Title: The summary of what needs to be done.
    • Description: Optional instructions.
    • Assign To: Choose a specific team member to assign the task to.
    • Due In: Set the number of hours after the trigger fires when the task becomes due (e.g., 24 hours).
  • Auto-linking: The task is automatically linked to the contact who triggered the automation, as well as any active deal context.

Agreement Actions

6. Send Agreement

Dispatches a digital agreement template to the contact for signing. The system automatically handles duplicate safety rules:

Existing Agreement StateAutomation System Action
Signed (Current Version)Skipped (does not resend).
Signed (Older Version)Creates and sends a new pending agreement for the current version.
Pending (Not yet signed)Resends the active signing link to remind the contact.
No prior agreementCreates and sends a new pending agreement.

Notification Actions

7. Send Notification

Sends an internal email alert when a trigger fires.

  • Recipients: You can select multiple workspace members and input external email addresses (like partners or vendors).
  • Email Content: The email is automatically generated and contains:
    • Contact Info: Name, email, and profile details of the contact.
    • Context: What event triggered the alert (e.g., "RSVP to Spring Gala").
    • Sales Details: If triggered by a deal change, it includes the deal name and currency-formatted deal value.
    • Purchase Details: If triggered by a product purchase, it includes the product name and the actual Amount Paid from the transaction history (rather than the catalog price).

Related

TriggersLoop Protection