Starting Steps
The starting step object is a trigger event that instantiates a workflow. The starting step always has a star in the header of the object:
There can only be one starting step in a workflow. The starting step cannot be deleted. Each starting step is a decision object (see below) and it has only one wire that leaves the object. The wire is green indicating the trigger occurred.
Starting steps cannot have incoming wires.
Type: Starting Step
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when the configured form is submitted. During the workflow, all elements of the form are queried using 'current form' filters.
Packages: Small Business Marketer, Corporate Marketer
Type: Starting Step
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when the configured contact history is detected.
Packages: Small Business Marketer, Corporate Marketer
Type: Starting Step
Visibility: Drip/Nurture Campaigns
Functionality: This starting step is triggered when a contact matches the defined query. The query is polled every 10 minutes.
Example: How do I trigger an email when a prospect moves into a new deal stage in Pipedrive?
Packages: Small Business Marketer, Corporate Marketer
Type: Starting Step
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when a contact is added to one of the selected lists. It is important to note that it is the addition of a new contact to the given list that causes the trigger. Thus existing contacts will not trigger this starting step unless they are removed from the list and re-added to the list.
Packages: Small Business Marketer, Corporate Marketer
Type: Starting Step
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when a contact is removed from one of the selected lists.
Packages: All Packages
Type: Starting Step
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when an incoming call or SMS message is received.
Packages: All Packages
Type: Starting Step
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when someone follows one of the configured account twitter handles.
Live Chat Detected
Packages: Small Business Marketer, Corporate Marketer
Type: Starting Step
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when an incoming chat is detected.
Packages: Small Business Marketer, Corporate Marketer
Type: Starting Step
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when a contact in your database visits a web page that matches the associated filter.
Packages: Small Business Marketer, Corporate Marketer
Type: Starting Step
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This starting step is triggered when an appointment is booked. Form elements are attached to all appointments and can be queried directly.
Packages: Small Business Marketer, Corporate Marketer
Type: Starting Step
Visibility: Drip/Nurture Campaigns
Functionality: This starting step is triggered when a contact(s) is added to the campaign by some user action. Users can be added to this campaign by:
- Manually adding a contact from the contact edit screen
- Adding a contact via the bulk contact edit (on the All Contacts screen)
- Using one of the Add To Campaign workflow actions
- Adding a contact(s) using the API
- Adding a contact using the Chrome Extension
Decisions
Decisions are objects that have one incoming wire and two outgoing wires. The decision object queries the contact currently being processed. If the query is true,
the path along the green wire leaving the decision object is followed. If the query is false
The path along the red wire leaving the decision object is followed. Clicking on the wire will give you the option to delete the wire or change the path state true/false
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This is a full query decision. You have full access to all contact meta-data/attributes and contact histories. If the query is true at the time of execution, the true path is followed. Refer to these articles to find out more about query building:
How do i use the query builder?
Packages: All
Type: Decision
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This checks to see if the contact being processed is currently a member of the selected list.
Packages: All
Type: Decision
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This checks to see if the contact opened a specific email at the time of processing. This decision has the option of adding a time element (i.e. wait for a specified time). If the wait is added, if the contact opens the specified email before the allotted time, the contact proceeds along the true path. If the time expires, it is assumed that the contact does not open the selected email. The icon changes if the time option is selected.
Packages: All
Type: Decision
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This checks to see if the contact clicked a specific link in an email at the time of processing. This decision has the option of adding a time element (i.e. wait for a specified time). If the wait is added, if the contact clicks the specified link before the allotted time, the contact proceeds along the true path. If the time expires, it is assumed that the contact does not click the link. The icon changes if the time option is selected.
Packages: All
Type: Decision
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This is a full query decision with a time element. You have full access to all contact meta-data/attributes and contact histories. If the query is true at the time of execution, the true path is followed. Refer to these articles to find out more about query building:
How do I use the query builder?
If query becomes true before the specified time, the true path is followed. If the query does not become true before the specified time, the false path is followed.
Packages: All
Type: Decision
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This is a full query decision with a time element. This wait is intended to wait for a history item that happens after the contact moves into the wait state.
If query becomes true before the specified time, the true path is followed. If the query does not become true before the specified time, the false path is followed.
Packages: Corporate Marketer
Type: Decision
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This checks to see if the contact visited a specified URL at the time of processing. This decision has the option of adding a time element (i.e. wait for a specified time). If the wait is added, if the visits the URL before the allotted time, the contact proceeds along the true path. If the time expires, it is assumed that the contact does visit the URL. The icon changes if the time option is selected.
Packages: Corporate Marketer
Type: Decision
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This checks to see if the contact attended the specified webinar at the time of processing.
Packages: Corporate Marketer
Type: Decision
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This checks to see if the contact registered for a specified webinar at the time of processing.
Actions
Actions are objects that take a specific action at the time the step is reached. An action object can only have one incoming wire and one outgoing wire. The outgoing wire for actions is Green.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This will send the configured email to the currently in-process contact.
Packages: Small Business Marketer, Corporate Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This will send the configured email to the currently in-process contact's related contact (as configured).
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will send the configured email to a list of employees of the account. You have three options with this:
- Send to an email list: You can select any list that has a target of 'Sales'. This option will send the configured email to any contact in the list that is an employee of the selected account
- Send to An Email Address: You can choose any employee in the selected account.
- Send to Assigned Sales Person: If the in-process contact has a contact manager, this configured email will be sent to that contact manager. If the in-process contact does not have an assigned contact manager, no email is sent.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will send the configured email to a list of employees of the account. You have three options with this:
- Send to an email list: You can select any list that has a target of 'Marketing'. This option will send the configured email to any contact in the list that is an employee of the selected account
- Send to An Email Address: You can choose any employee in the selected account.
- Send to Assigned Sales Person: If the in-process contact has a contact manager, this configured email will be sent to that contact manager. If the in-process contact does not have an assigned contact manager, no email is sent.
This action is identical to the Email Sales action, with the one major difference: If an email is sent using the Email Marketer action, the reporting engine will NOT register the in-process contact as a Sales Ready Lead. Thus this step is typically used to communicate activity to the employees of the account without impacting any of the reports.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, Drip Campaigns
Functionality: This will send the configured email (and dynamically generated report) to the in-process contact. This workflow action allows you to send prospects PDF reports that are based data collected on the prospect.
Packages: All
Type: Action
Visibility: Appointment Processing Workflow
Functionality: This will send the configured email to the configured scheduler employee.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This will send the configured email to the prospect and will attach the prospect's current data history. This is used in a GDPR request for personal information data requests. This will log a history item on the prospect's timeline thus providing an audit trail of complying with GDPR request for information requests.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This will add the configured tag to the in-process contact.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This will remove the configured tag from the in-process contact.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action stops the processing of the prospect until the specified time. This action has a feature called 'predictive send'. ActiveDEMAND collects data on all prospects. The predictive send will use this data to predict when is the right time to proceed based on the patterns of engagement with the prospect.
Wait for Time:
Contact enters the workflow and waits the configured time. After the contact has been in the wait state for the specified time (and no Predictive options are chosen), the contact proceeds to the next step.
Wait for weekday/time
Contact enters the workflow and waits for the first selected day and the actual time configured. After the contact has been in the wait state for the specified time (and no Predictive options are chosen), the contact proceeds to the next step. Note: configured time is the "marketer's" timezone.
Wait for this day of the month:
Contact enters the workflow and waits for the first configured day of the month and the actual time configured. After the contact has been in the wait state for the specified time (and no Predictive options are chosen), the contact proceeds to the next step. Note: configured time is the "marketer's" timezone.
Predictive Wait:
If you choose wait for the predicted Best Send Time, there could be up to 24 hours additional wait time added if the AD algorithm determines the right time of day is 23 hours and 59 seconds in the future. If you choose wait for the predicted Best Send Day, there could be an additional 6 days added to the wait if the AD algorithm determines the best send day as being 6 days in the future.
Packages: Small Business Marketer, Corporate Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will create a related contact to the in-process contact based on the relationship configuration.
Preconditions: The in-process contact is not an employee, the related contact is not an employee
Packages: Corporate Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action posts to the configured webhook.
Preconditions: The webhook is set up correctly with the proper JSON payload, target URL, headers, (and if required) basic auth.
Packages: Corporate Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action allows you to assign the in-process contact to an employee using different strategies:
- Round Robin: assigns leads to employees in a defined sales list based on round-robin logic
- Sales Activity: This assigns leads to the top-performing salesperson within a sales list. Performance can be measured based on completed activities by the salesperson or using custom rep scoring logic.
Preconditions: The in-process contact is not an employee
Packages: Small Business Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action takes a screenshot of a defined web asset and attaches the file to a 'file' custom field on the in-process contact. The action has two modes
- URL: Takes a screenshot of the giving url
- Dynamic Block: This takes a screen capture of a dynamic block. This mode allows you to take complex designs with personalization and embed the image in an email etc
Preconditions: In-process, contact has a defined 'file' custom field
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: If this contact has a Twitter handle, this action will send the in-process contact a direct Twitter message.
Preconditions: There is a configured Twitter account in the account settings.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: If this contact has a twitter handle, this action will follow the in-process contact.
Preconditions: There is a configured Twitter account in the account settings.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: If this contact has a twitter handle, this action will unfollow the in-process contact.
Preconditions: There is a configured Twitter account in the account settings.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will add the in-process contact from the selected Static list. Contacts can only be inserted directly into Static lists. Dynamic lists have a query that governs the list member's, thus there is no way to directly insert a prospect into a Dynamic list.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will remove the in-process contact from the selected Static list. Contacts can only be removed directly from Static lists. Dynamic lists have a query that governs the list member's, thus there is no way to directly remove a prospect from a Dynamic list.
Packages: Corporate Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will add/subtract the configured value from the in-process contact's lead score. Lead scores cannot go over 100, or less than zero.
Packages: Corporate Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will register the in-process contact in the configured webinar
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will create/update the in-process contact in Pipedrive and create/update an associated deal.
Preconditions: There is a configured Pipedrive account in the account settings. The contact must have a defined contact manager or a selected Pipedrive user. All posts to Pipedrive must be associated with a Pipedrive user account. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated user, this will not post to Pipedrive. Posting to Pipedrive will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will schedule the configured activity on the in-process contact in Pipedrive
Preconditions: There is a configured Pipedrive account in the account settings. The contact must have a defined contact manager or a selected Pipedrive user. The contact must exist in Pipedrive before this action is called. All posts to Pipedrive must be associated with a Pipedrive user account.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will set the specified field on the contact/org/deal
Preconditions: There is a configured Pipedrive account in the account settings. The contact must have a defined contact manager or a selected Pipedrive user. The field must be read/write for the specified field. The contact must exist in Pipedrive before this action is called.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to PipelineDeals and create/update an associated deal
Preconditions: There is a configured PipelineDeals account in the account settings. The contact must have a defined contact manager or a selected PipelineDeals user. All posts to PipelineDeals must be associated with a PipelineDeals user account. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated user, this will not post to PipelineDeals. Posting to PipelineDeals will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will post the configured Task on the in-process contact in PipelineDeals
Preconditions: There is a configured PipelineDeals account in the account settings. The contact must have a defined contact manager or a selected PipelineDeals user. All posts to PipelineDeals must be associated with a PipelineDeals user account.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will schedule the configured activity on the in-process contact in PipelineDeals
Preconditions: There is a configured PipelineDeals account in the account settings. The contact must have a defined contact manager or a selected PipelineDeals user. All posts to PipelineDeals must be associated with a PipelineDeals user account.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will schedule the configured activity on the in-process contact in Enquire CRM
Preconditions: There is a configured Enquire account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows
Functionality: This will post the in-process contact to Enquire CRM and create/update an associated prospect
Preconditions: There is a configured Enquire account in the account settings. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated prospect, this will not post to Enquire. Posting to Enquire will be viewed as making the in-process contact as a Sales Ready Lead for reports
Packages: All
Type: Action
Visibility: Lead Processing Workflows
Functionality: This will post to the Enquire notifications system
Preconditions: There is a configured Enquire account in the account settings. This action will not post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated prospect, this will not post to Enquire.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, drip campaigns
Functionality: This will set the specified field on the in process contact
Preconditions: There is a configured Enquire account in the account settings. This action will not post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings).
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to noCrm.io and create/update an associated deal
Preconditions: There is a configured noCrm.io account in the account settings. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped this will not post to noCrm.io. Posting to noCrm.io will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will post the in-process contact and contact history to Eldermark CRM
Preconditions: There is a configured Eldermark CRM account in the account settings. The contact history will only post if it is one of submitted form, email open, email link click, chat, phone call, text message, or unsubscribe.
Post contact to Nimble
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to Nimble
Preconditions: There is a configured Nimble account in the account settings. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped this will not post to Nimble. Posting to Nimble will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Type: Action
Visibility: Lead Processing Workflows, Campaigns
Functionality: This will the configured specified contact field on the in-process contact in Nimble
Preconditions: There is a configured Nimble account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will post/schedule the configured Task on the in-process contact in Nimble
Preconditions: There is a configured Nimble account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to Freshsales and create/update an associated deal
Preconditions: There is a configured Freshsales account in the account settings. The contact must have a defined contact manager or a selected Freshsalesuser. All posts to Freshsales must be associated with a Freshsales user account. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated user, this will not post to Freshsales. Posting to Freshsales will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will post/schedule the configured Task on the in-process contact in Freshsales
Preconditions: There is a configured Freshsales account in the account settings and the in process contact exists in Freshsales.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns, Autoresponders
Functionality: This will post/schedule the configured Activity on the in-process contact in Freshsales
Preconditions: There is a configured Freshsales account in the account settings and the in process contact exists in Freshsales.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer: Autoresponders, Drip Campaigns)
Functionality: This will create the configured Lead in Freshsales. f fields are not mapped or if there is not an associated user, this will not post to Freshsales. Posting to Freshsales will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Preconditions: There is a configured Freshsales account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, Drip Campaigns
Functionality: This will schedule the configured Appointment on the in-process contact in Freshsales
Preconditions: There is a configured Freshsales account in the account settings and the in process contact exists in Freshsales.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer: Autoresponders, Drip Campaigns)
Functionality: This will set the specified field on the object specified in FS.
Preconditions: There is a configured Freshsales account in the account settings.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, Drip Campaigns
Functionality: This will create/schedule a call activity on the in-process contact in Salesforce
Preconditions: There is a configured SalesForce account in the account settings. The contact must have a defined contact manager. All posts to SalesForce must be associated with a SalesForce user account.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, Drip Campaigns
Functionality: This will set the specified SalesForce field on the in-process contact in Salesforce
Preconditions: There is a configured SalesForce account in the account settings. The contact must have a defined contact manager. All posts to SalesForce must be associated with a SalesForce user account.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, Drip Campaigns
Functionality: This will create/schedule an event on the in-process contact in Salesforce
Preconditions: There is a configured SalesForce account in the account settings. The contact must have a defined contact manager. All posts to SalesForce must be associated with a SalesForce user account.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, Drip Campaigns
Functionality: This will create/schedule a task on the in-process contact in Salesforce
Preconditions: There is a configured SalesForce account in the account settings. The contact must have a defined contact manager. All posts to SalesForce must be associated with a SalesForce user account.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, Drip Campaigns
Functionality: This will create an opportunity with the in process contact.
Preconditions: The in process contact is not a lead in SalesForce. The contact must have a defined contact manager. All posts to SalesForce must be associated with a SalesForce user account.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to Salesforce and create/update an associated lead/contact. You can create a Lead or a Contact using this object. You cannot convert a Lead to a contact, but you can set the lead status and/or update the contact/lead. When calling this, the field mapping in the account settings will be used.
Preconditions: There is a configured SalesForce account in the account settings. The contact must have a defined contact manager. All posts to SalesForce must be associated with a SalesForce user account. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated user, this will not post to SalesForce . Posting to SalesForce will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to Microsoft Dynamics and create/update an associated opportunity
Preconditions: There is a configured Microsoft Dynamics account in the account settings. The contact must have a defined contact manager. All posts to Microsoft Dynamics must be associated with a Microsoft Dynamics user account. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated user, this will not post to Microsoft Dynamics. Posting to Microsoft Dynamics will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to Microsoft Dynamics and create/update the Lead.
Preconditions: There is a configured Microsoft Dynamics account in the account settings. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated user, this will not post to Microsoft Dynamics. Posting to Microsoft Dynamics will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, Campaigns
Functionality: This will post/schedule the configured Task on the in-process contact in Microsoft Dyanamics
Preconditions: There is a configured Microsoft Dyanamics account in the account settings.
Packages: Corporate Marketer
Type: Action
Visibility: Lead Processing Workflows, Drip Campaigns
Functionality: This will set the specified field on the object specified in Microsoft Dynamics.
Preconditions: There is a configured Microsoft Dynamics account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to Zoho CRM and create/update an associated deal
Preconditions: There is a configured Zoho CRM account in the account settings. The contact must have a defined contact manager or a selected Zoho Sales User. All posts to Zoho CRM must be associated with a Zoho CRM user account. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated user, this will not post to Zoho CRM . Posting to Zoho CRM will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Campaigns
Functionality: This will post/schedule the configured Task on the in-process contact in Zoho CRM
Preconditions: There is a configured Zoho CRM account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer: Autoresponders, Drip Campaigns)
Functionality: This will post/schedule the configured Task on the in-process contact in Zoho CRM
Preconditions: There is a configured Zoho CRM account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Drip Campaigns
Functionality: This will set the specified field on the object specified in Zoho CRM.
Preconditions: There is a configured Zoho CRM account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Drip Campaigns, Autoresponders
Functionality: Will post a call object to the contact
Preconditions: There is a configured Zoho CRM account in the account settings.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, (Corporate Marketer Package: Autoresponders, Drip Campaigns)
Functionality: This will post the in-process contact to SherpaCRM and create/update an associated deal
Preconditions: There is a configured SherpaCRM account in the account settings. The contact must have a defined contact manager or a selected SherpaCRM user. All posts to SherpaCRM must be associated with a SherpaCRM user account. This action will post the mapped fields set up in the field mapping configuration screen in the account settings (Administration-account settings). If fields are not mapped or if there is not an associated user, this will not post to SherpaCRM. Posting to SherpaCRM will be viewed as making the in-process contact as a Sales Ready Lead for reports.
Packages: All
Type: Action
Visibility: Lead Processing Workflows, Autoresponders, Drip Campaigns
Functionality: This will schedule the configured Appointment on the in-process contact in Sherpa CRM.
Preconditions: There is a configured Sherpa CRM account in the account settings and the in process contact exists in Sherpa.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will set the utm_source and utm_medium for the current contact history for the in-process contact.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: If the in-process contact has a phone number, this action will send the in-process contact an sms/mms message
Preconditions: There is a local number that supports SMS/MMS set up in the Assets-Call Tracking Numbers and the number is not currently in a DNI group.
Packages: All
Type: Action
Visibility: Lead Processing Workflows
Functionality: If the configured employee has a phone number, this action will send selected employee an sms/mms message
Preconditions: There is a local number that supports SMS/MMS set up in the Assets-Call Tracking Numbers and the number is not currently in a DNI group.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: If the configured in-process contact has a phone number, this action will call the in-process contact
Preconditions: There is a number set up in the Assets-Call Tracking Numbers
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will set a named date for the in-process contact.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will set the specified Custom Field for the in-process contact.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will set the specified Standard Field for the in-process contact.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will create a 'Won Deal' history item for the in-process contact. This will register a 'Won Deal' for drill down reports.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will execute a 'forget me' action and post the contact to the 'Administration-Forget me requests' table in ActiveDEMAND. This provides full auditing of data deletion requests.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will post an Event to Google Analytics using the in-process contact's (if available) Google GCID. Note, that there is a time limit as to how long you can wait before posting the event to Google Analytics (2 weeks?) or Google will not associate the session with the event.
Preconditions: There is an authorized Google account set in the Account settings.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will post a Transaction to Google Analytics using the in-process contact's (if available) Google GCID.
Preconditions: There is an authorized Google account set in the Account settings.
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will post a Transaction to Google Adwords using the in-process contact's data
Preconditions: There is an authorized Google account set in the Account settings.
Goal Completion
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will create a Goal Completion history item for the prospect
Preconditions: There is a defined campaign with at least one defined goal
Packages: All
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This action will pull external data for the in-process contact/organization. This will use data enrichment credits.
Preconditions: There are data enrichment credits available
Packages: Small Business Marketer, Corporate Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This adds the contact to the selected User Drip campaign.
Packages: Small Business Marketer, Corporate Marketer
Type: Action
Visibility: Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows
Functionality: This removes the contact from the selected User Drip campaign.
Type: Action
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows, Autoresponders
Functionality: Posts a message to the selected slack channel
Type: Action
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows, Autoresponders
Functionality: Creates a calendar appointment on the associated calendar. You can connect any calendar that is currently linked to an employee's appointment scheduler. This will post an event contact history type on the in process contact's timeline.
Type: Action
Visibility: Drip/Nurture Campaigns, Lead Processing Workflows, Autoresponders
Functionality: Operates on custom fields of the type 'Numeric'. This will replace the numeric custom field value with a new value that is a calculation defined in the options panel.
Comments
Please sign in to leave a comment.