Sending campaigns
Depending on the use case, campaign administrators must set up different campaign triggers:
Manual
Scheduled
Remote action
API
Workflows
These settings determine how you can send a campaign to employees.
Only published campaigns are available to target employees.
Campaign sending methods
Sending a campaign manually
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.
Sending a campaign manually on VDI sessions
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.
Sending a scheduled campaign
Scheduled campaigns do not require manual triggering. Once the campaign is published, it is sent automatically according to the configuration defined in the Schedule tab.
The system evaluates the defined NQL query based on the selected schedule and sends the campaign to the resulting employees.
Depending on the configured campaign retargeting rule, the query will be re-evaluated relative to the time it was first published, daily or hourly.
For more information on scheduling and reevaluation, refer to the Campaign scheduling documentation.
Sending a remote action campaign
After a remote action campaign is published, add its NQL ID to the remote action’s scripts to trigger the campaign.
Refer to Remote action campaign configuration documentation.
Sending a campaign using the API
Trigger campaigns using the Nexthink Campaigns API, which enables integrations with external applications.
Refer to developer.nexthink.com for more information.
Sending a campaign using a workflow
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.
Refer to Workflow campaign configuration for more information.
Parametrized campaigns
Manual, API, and workflow campaigns can be parameterized. In such cases, users who trigger the campaign manually or systems that execute it via an API call must provide the required input values.
Refer to Configuring campaign parametersfor more information.
RELATED TOPICS:
Last updated
Was this helpful?