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:

blob1477939174820.png


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.

blob1477938979048.png


Starting steps cannot have incoming wires.



.


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 a contact using the Chrome Extension




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.



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, 


blob1477938979048.png


the path along the green wire leaving the decision object is followed. If the query is false


blob1477939039526.png


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


blob1477939120254.png


blob1478223196001.png

Type: Decision

Visibility:  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.



Type: Decision

Visibility:  Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This checks to see if the contact being processed is currently a member of the selected list. 



Type: Decision

Visibility:  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.



Type: Decision

Visibility:  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.



Type: Decision

Visibility:  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. 


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.



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. 




Type: Action

Visibility:  Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This will send the configured email to the currently in-process contact.



Type: Action

Visibility: Lead Processing Workflows, 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 Sales Ready Lead. Thus this step should only be used if you are looking to measure the number of Sales Ready Leads being generated.



Type: Action

Visibility: Lead Processing Workflows, 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.



Type: Action

Visibility: Appointment Processing Workflow

Functionality: This will send the configured email to the configured scheduler employee.



Type: Action

Visibility:  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.



Type: Action

Visibility:  Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This will add the configured tag to the in-process contact.



Type: Action

Visibility:  Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This will remove the configured tag from the in-process contact.



Type: Action

Visibility:  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.

If you choose wait for the predicted Best Send Time, there could be up to 24 hours additional wait time added if the FF 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 FF algorithm determines the best send day as being 6 days in the future.



Type: Action

Visibility:  Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This will send a tweet.
Preconditions: There is a configured Twitter account in the account settings.



Type: Action

Visibility:  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.



Type: Action

Visibility:  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.



Type: Action

Visibility:  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.



Type: Action

Visibility:  Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This will post a shared article to LinkedIn
Preconditions: There is a configured LinkedIn account in the account settings.



Type: Action

Visibility:  Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This will post a shared article to Facebook
Preconditions: There is a configured Facebook account in the account settings.






Type: Action

Visibility:  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.



Type: Action

Visibility:  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.



Type: Action

Visibility:  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.



Type: Action

Visibility:  Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This action will register the in-process contact in the configured webinar



Type: Action

Visibility: Lead Processing Workflows, Drip Campaigns)

Functionality: This will post the in-process contact to 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.



Type: Action

Visibility: Lead Processing Workflows, Campaigns

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. 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 user



Type: Action

Visibility: Lead Processing Workflows, 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.



Type: Action

Visibility: Lead Processing Workflows, Campaigns

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. 



Type: Action

Visibility: Lead Processing Workflows, Campaigns

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. 




Type: Action

Visibility: Lead Processing Workflows, Campaigns

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. 



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


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). 


Type: Action

Visibility: Lead Processing Workflows, 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.



Type: Action

Visibility: Lead Processing Workflows, Campaigns

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

Type: Action

Visibility: Lead Processing Workflows, 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.


Type: Action

Visibility: Lead Processing Workflows, Campaigns

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.



Type: Action

Visibility: Lead Processing Workflows, 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.





Type: Action

Visibility: Lead Processing Workflows, Campaigns

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.



Type: Action

Visibility: Lead Processing Workflows, Campaigns

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.


Type: Action

Visibility: Lead Processing Workflows,  Drip Campaigns

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.




Type: Action

Visibility: Lead Processing Workflows, 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.



Type: Action

Visibility: Lead Processing Workflows, 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: All

Type: Action

Visibility: Lead Processing Workflows,   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: All

Type: Action

Visibility: Lead Processing Workflows,  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.


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.


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.





Type: Action

Visibility: Lead Processing Workflows, 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.





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.





Type: Action

Visibility: Lead Processing Workflows,  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.






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.




Type: Action

Visibility: Lead Processing Workflows, Drip Campaigns

Functionality: Will post a call object to the contact
Preconditions: There is a configured Zoho CRM  account in the account settings.


Type: Action

Visibility: Lead Processing Workflows,   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, 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: 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: All

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: All

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. 


Type: Action

Visibility:  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.



Type: Action

Visibility:   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.



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.



Type: Action

Visibility:   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



Type: Action

Visibility:   Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This action will set a named date for the in-process contact.



Type: Action

Visibility:   Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This action will set the specified Custom Field for the in-process contact.



    

Type: Action

Visibility:   Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This action will set the specified Standard Field for the in-process contact.



Type: Action

Visibility:   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.



Type: Action

Visibility:   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.



Type: Action

Visibility:   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.



Type: Action

Visibility:   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.



Goal Completion

Type: Action

Visibility:   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



Type: Action

Visibility:   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



Type: Action

Visibility:   Drip/Nurture Campaigns, Lead Processing Workflows

Functionality: This adds the contact to the selected User Drip campaign.


Type: Action

Visibility:   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

Functionality: Posts a message to the selected slack channel