Triggering campaigns
Last updated
Was this helpful?
Last updated
Was this helpful?
Refer to the Launching campaign programs documentation for guidelines on planning, gaining approval, testing and launching your campaign within your organization.
Depending on the type of your campaign, you must set up different campaign triggers: manual, scheduled, remote action, or via API.
Before manually triggering a campaign, you must first:
Grant Trigger manually all campaigns or share a campaign with trigger permission.
Configure the campaign for a Manual trigger. Refer to the Manage Campaigns documentation for more information.
From the Investigations page, after running an NQL investigation query listing Users:
Select a user or a set of users from the investigation results table.
Execute actions from the action bar at the bottom of the page. The Select action pop-up displays the list of available actions, including campaigns.
Select the campaign and Run on user(s).
The Send campaign pop-up displays the number of targeted employees. If the campaign has parameters, you must provide a value for each parameter before confirming Yes, send to user(s).
If all employees have a valid user SID, a validation message confirms the system has triggered the campaign.
If there is a mix of employees with valid or invalid SIDs, a warning message confirms that the system can only trigger the campaign for those employees with valid SIDs.
If all employees have an invalid SID, an error message confirms that the system cannot trigger the campaign.
Refer to Types of campaigns documentation for information on parameters for manual and API campaigns.
If you are using VDI, run an investigation using the NQL editor or Visual editor:
Query a list of VDI sessions.
Select one or multiple sessions from the investigation results table, and Execute actions—using the action bar.
Select the campaign of interest, identifiable by a chat icon, and run on the selected sessions.
Only campaigns configured for VDI can run on sessions.
Once you publish a scheduled campaign, the evaluation of the NQL query defined in the Schedule tab of the Edit campaign page begins.
The query will be re-evaluated relative to the time it was first published, daily or hourly, depending on the option Only once or Again after that was selected, according to the rules detailed in the Schedule section in the documentation.
Once you have published a remote action campaign, add its NQL ID to the remote action’s scripts to trigger the campaign.
Select Campaigns from the main menu.
Click on Manage campaigns in the navigation panel.
Click on the title of the campaign you wish to connect to.
Copy the NQL ID value from the NQL ID field in the General tab of the configuration page.
Paste the value into your remote action script. Refer to the following documentation for details:
Nexthink recommends using NQL ID as a campaign identifier if you use Collectors version 23.5 or higher. You can still use campaign UID for compatibility reasons.
Select Campaigns from the main menu.
Choose the campaign you wish to connect to from the navigation menu.
Locate the UID of the campaign as part of the URL and copy it for the remote action.
Trigger campaigns using the Nexthink Campaigns API, which allows you to create integrations with external applications. For parametric campaigns, specify the values of each parameter. Visit the developer.nexthink.com website to learn more.
Trigger campaigns using the Nexthink Workflow API to notify employees about remediations that are taking place, or to prompt for permission or additional information that a workflow needs to continue running an automated remediation.
To use a campaign in a workflow, ensure that:
The workflow trigger is set.
The campaign contains only single answer questions.
The campaign is published.
