--- title: "FunnelFLARE workflow Reference" canonical: "https://funnelflare-engagement-center.refined.site/space/STARTTHEFIRE/170787384/FunnelFLARE%20workflow%20Reference" format: markdown --- ![image]() **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: ![image]()   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.** ![image]() Starting steps **cannot** have incoming wires. ![image]() **Name: **Form Submitted   **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. ![image]() **Name: **New Contact History **Type: **Starting Step **Visibility: **Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This starting step is triggered when the configured contact history is detected.  ![image]() **Name: **Contact Changed **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. ![image]() **Name: **Added To List **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.  ![image]() **Name: **Removed From List **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.  ![image]() **Name: **Incoming Call **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.  > Macro (inline-external-image) **Name:** Live Chat Detected  **Type: **Starting Step **Visibility: **Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This starting step is triggered when an incoming chat is detected.  ![image]() **Name: **Page Visit **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. ![image]() **Name: **New Appointment **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. ![image]() **Name: **Deal Changed **Packages: **Small Business Marketer, Corporate Marketer **Type: **Starting Step **Visibility: **Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This starting step is triggered when a deal is created, the status is changed, or the stage is changed ![image]() **Name: **User Triggered Campaign **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,  ![image]() the path along the** green wire leaving** the decision object is followed. If the query is false ![image]() 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 ![image]() ![image]() **Name: **Decision **Type: **Decision **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?](/wiki/spaces/*/pages/170066298) ![image]() **Name: **Is a member of list **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.  ![image]() ![image]() **Name: **Email Opened **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. ![image]() ![image]() **Name: **Email Link Clicked **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. ![image]() **Name: **Wait for Change **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?](https://engage.activedemand.com/hc/en-us/articles/360046523354) If the 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. ![image]() **Name: **Wait for Next **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 the 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. ![image]() **Name: **Split Test **Packages: **All **Type: **Decision **Visibility: **Drip/Nurture Campaigns, Lead Processing Workflows **Functionality:  **This decision randomly switches between two paths. ![image]() ![image]() **Name: **Page Visit **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 **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. ** ![image]()   ![image]() **Name: **Email Prospect **Type: **Action **Visibility: **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This will send the configured email to the currently in-process contact. ![image]() **Name: **Email Related Prospect **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). ![image]() **Name: **Email Sales **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. This action is identical to the Email Marketer action, with the one major difference: If an email is sent using the Email Sales action, the reporting engine will register the in-process contact as a **Market Qualified Lead. **Thus this step should only be used if you are looking to measure the number of Market Qualified Leads being generated. ![image]() **Name: **Email Marketer **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 **Market Qualified Lead. **Thus this step is typically used to communicate activity to the employees of the account without impacting any of the reports. ![image]() **Name: **Send Report **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.  ![image]() **Name: **Email Sender **Type: **Action **Visibility: **Appointment Processing Workflow **Functionality: **This will send the configured email to the configured scheduler employee. ![image]() **Name: **Email Contact Export **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 requests for information requests. ![image]() **Name: **Tag Prospect **Type: **Action **Visibility: **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This will add the configured tag to the in-process contact. ![image]() **Name: **Remove Tag **Type: **Action **Visibility: **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This will remove the configured tag from the in-process contact. ![image]() **Name: **Wait **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'. FunnelFLARE 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:* ![image]() 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* ![image]() 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:* ![image]() 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:* ![image]() If you choose to 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 to 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. ![image]() **Name: **Create Related Contact **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 ![image]() **Name: **Remove Contact Relationship **Type: **Action **Visibility: **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This action will remove all contact relationships the in-process contact that matches the configured query to **Preconditions: **The in-process contact is not an employee, the related contact is not an employee ![image]() **Name: **Post To External WebHook **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. ![image]() **Name: **Assign Contact Manager **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 ![image]() **Name: **Screen Capture Webpage **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    ![image]() **Name: **Add To List **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. ![image]() **Name: **Remove From List **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. ![image]() **Name: **Adjust Lead Score **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. ![image]() **Name: **Post To Pipedrive **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 **Market Qualified Lead** for reports. ![image]() **Name: **Create Pipedrive Activity **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.  ![image]() **Name: **Set Field **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. ![image]() **Name: **Post to PipelineDeals **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 Market Qualified Lead for reports. ![image]() **Name: **Post PipelineDeals Task **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.  ![image]() **Name: **Post PipelineDeals Activity **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.  ![image]() **Name: **Post Activity to Enquire **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.  ![image]() **Name: **Post Contact to Enquire **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 **Market Qualified Lead** for reports ![image]() **Name: **Post Notification to Enquire **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.  ![image]() **Name: **Set Enquire Field **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).  ![image]() **Name: **Post to noCRM **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 **Market Qualified Lead** for reports. ![image]() **Name: **Post To Eldermark CRM **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. ![image]() **Name:** Post contact to Nimble **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 **Market Qualified Lead** for reports. ![image]() **Name:** Set Field **Type: **Action **Visibility: **Lead Processing Workflows, Campaigns, Autoresponders **Functionality: **This will set the specified field on the in-process contact in Nimble **Preconditions: **There is a configured Nimble account in the account settings. ![image]() **Name:** Create Nimble Task **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. ![image]() **Name:** Freshsales Deal **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 **Market Qualified Lead** for reports. ![image]() **Name:** Freshsales Task **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. ![image]() **Name:** Freshsales Activity **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. ![image]() **Name:** Freshsales Lead **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 **Market Qualified Lead** for reports. **Preconditions: **There is a configured Freshsales account in the account settings. ![image]() **Name:** Freshsales Appointment **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. ![image]() **Name:** Freshsales Set Field   **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. ![image]() **Name:** SalesForce Log Call **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.  ![image]() **Name:** Set SalesForce Field **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.  ![image]() **Name:** SalesForce Event **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.  ![image]() **Name:** Add To Campaign **Type: **Action **Visibility: **Lead Processing Workflows, Autoresponders, Drip Campaigns **Functionality: **This will add the in-process contact to the selected Salesforce Campaign with the selected status. **Preconditions: **There is a configured SalesForce account in the account settings. The contact must have a defined contact manager. The contact must be either a Lead or Contact in Salesforce before the action is called. The contact must not already be in the selected Salesforce campaign. All posts to SalesForce must be associated with a SalesForce user account.  ![image]() **Name:** Create Salesforce Task **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.  ![image]() **Name:** Create Salesforce Opportunity **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.  ![image]() **Name:** Post To SalesForce **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 **Market Qualified Lead** for reports. ![image]() **Name:** Dynamic Post Contact **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 **Market Qualified Lead** for reports. ![image]() **Name:** Dynamics Post Lead **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 **Market Qualified Lead** for reports. ![image]() **Name:** Dynamics Schedule Task **Type: **Action **Visibility: **Lead Processing Workflows, Campaigns **Functionality: **This will post/schedule the configured Task on the in-process contact in Microsoft Dynamics **Preconditions: **There is a configured Microsoft Dynamics account in the account settings. ![image]() **Name:** MS Dynamics Set Field **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. ![image]() **Name:** Zoho CRM Post Contact   **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 **Market Qualified Lead** for reports. ![image]() **Name:** Zoho CRM Task   **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. ![image]() **Name:** Zoho CRM Post Lead   **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. ![image]() **Name:** Zoho Set Field   **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. ![image]() **Name:** Zoho CRM Call   **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. ![image]() **Name:** Post to SherpaCRM **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 **Market Qualified Lead** for reports. ![image]() **Name:** Sherpa Sales Activity **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. ![image]() **Name:** Set Source **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. ![image]() **Name:** Sms/MMS Message Prospect **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. ![image]() **Name:** SMS/MMS Message Sales **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. ![image]() **Name:** Make Call **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 ![image]() **Name:** Set Date **Type: **Action **Visibility: **** **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This action will set a named date for the in-process contact. ![image]() **Name:** Set Custom Field **Type: **Action **Visibility: **** **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This action will set the specified Custom Field for the in-process contact. ![image]()      **Name:** Set Field **Type: **Action **Visibility: **** **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This action will set the specified Standard Field for the in-process contact. ![image]() **Name:** Create Order **Type: **Action **Visibility: **** **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This action will create a 'Sales Order' history item for the in-process contact. This will register a 'Sales Order' for drill-down reports. ![image]() **Name:** Forget Contact **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 FunnelFLARE. This provides full auditing of data deletion requests. ![image]() **Name:** Goal Completion **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 ![image]() **Name:** Data Enrichment **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 ![image]() **Name:** Add to Campaign **Type: **Action **Visibility: **** **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This adds the contact to the selected User Drip campaign. ![image]() **Name:** Remove from Campaign **Type: **Action **Visibility: **** **Autoresponders, Drip/Nurture Campaigns, Lead Processing Workflows **Functionality: **This removes the contact from the selected User Drip campaign. ![image]()   **Name:** Slack Message **Type: **Action **Visibility: **** ** Drip/Nurture Campaigns, Lead Processing Workflows, Autoresponders **Functionality: **Posts a message to the selected slack channel     ![image]() **Name:** Schedule Event **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.     ![image]() **Name:** Custom Calculation **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.