STEP 1
Connect Currents and Lansweeper
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Currents and Lansweeper Integration
Build developer tools workflows between Currents and Lansweeper on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Currents and Lansweeper
Detailed info you need to know about Currents and Lansweeper integrations in WEXTL. Explore which modules apps support and how you connect them.
Currents
Track Cypress and Playwright test runs in Currents — read runs, tests, errors, and insights, manage actions, and react to run events. [5]
Lansweeper
IT asset discovery and management platform for inventory, scanning, and reporting. [6]
How to connect Currents to Lansweeper
Set up your Currents and Lansweeper integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Currents and Lansweeper nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Currents and Lansweeper. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Currents and Lansweeper work in WEXTL?
WEXTL exposes actions and triggers for Currents and Lansweeper that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Currents triggersLansweeper actions
Currents modules
- Cancel RunCancels a run that is still in progress.
- Cancel Run by GitHub CICancels a run identified by its GitHub Actions workflow run.
- Create ActionCreates a new action that quarantines, skips, or tags matching tests.
- Create Jira IssueCreates a Jira issue from a test in a run and links it back.
- Delete ActionArchives an action so it stops applying to tests.
- Delete Project TermDeletes a tag term from a project's filter list.
- Delete RunDeletes a run and all of its associated data.
- Disable ActionDisables an action without archiving it.
- Enable ActionEnables an action that is currently disabled.
- Find RunReturns the most recent completed run matching the criteria.
- Generate Test SignatureComputes the stable signature for a test from its project, spec file, and title.
- Get ActionReturns a single action by its identifier.
- Get Affected Test ExecutionsRetrieves the executions of one affected test in a date range.
- Get InstanceReturns a single spec-file instance with its test results.
- Get ProjectReturns a single project by its identifier.
- Get Project InsightsReturns aggregated run and test metrics for a project.
- Get RunReturns a single run with its groups and spec results.
- Get Test Failure ContextReturns structured failure context for a run, a spec file, or a single test.
- Get Test ResultsRetrieves the historical executions of one test signature.
- Get WebhookReturns a single webhook by its identifier.
- Link Jira IssueLinks an existing Jira issue to a test in a run.
- List Action Test ExecutionsRetrieves the test executions where one action was applied.
- List ActionsRetrieves the actions configured for a project.
- List Affected TestsRetrieves the tests affected by actions in a date range.
- List ErrorsRetrieves errors from the Errors Explorer for a project.
- List Jira Issue TypesRetrieves the Jira issue types available for a Jira project.
- List Jira ProjectsRetrieves the Jira projects available to the connected Jira integration.
- List Project RunsRetrieves the test runs recorded for a project.
- List Project TermsRetrieves the filter terms of one kind recorded for a project.
- List ProjectsRetrieves the projects in your Currents organization.
- List Pull RequestsRetrieves the pull requests with run activity for a project.
- List Spec FilesRetrieves spec files from the Spec Files Explorer for a project.
- List TestsRetrieves tests from the Tests Explorer for a project.
- List WebhooksRetrieves the webhooks configured for a project.
- Make an API CallPerforms an arbitrary authorized API call.
- Reset RunResets failed spec files in a run so they can run again.
- Update ActionUpdates an existing action.
- Update WebhookUpdates the URL, events, headers, or label of a webhook.
- Watch EventsTriggers when a test run starts, finishes, times out, or is cancelled.
Lansweeper modules
- Check an Export RequestChecks the status of an export request.
- Create a RelationCreates a new relation between entities.
- Create a Scanning TaskCreates a scanning task.
- Create an AssetCreates a new asset in the system.
- Create Site's Custom FieldsCreates custom fields for a specified site.
- Delete an Asset ResourceDeletes an asset resource.
- Delete Custom FieldsDeletes a site's custom fields.
- Delete RelationsDeletes relations between specified entities or objects.
- Export a RequestExports a request to a specified format or system.
- Get a Full Report ExecutionRetrieves the execution details of a full report.
- Get a Report ExecutionRetrieves a report execution result.
- Get a Site's InformationRetrieves a site's information.
- Get Asset DetailGets an asset resource.
- Get Full Report StatusRetrieves the full status of a report.
- Get Report StatusRetrieves the status of a report.
- Get Site Custom FieldsRetrieves custom fields configured for a site.
- Get Software DetailsRetrieves the details of a specific software.
- List Asset GroupsRetrieves information about all asset groups.
- List Asset Groups with SoftwareRetrieves asset groups that contain software.
- List Asset Groups Without SoftwareRetrieves asset groups that do not contain software installed.
- List Asset ResourcesRetrieves assets available in the installation.
- List Asset StatesRetrieves a list of asset states from the service.
- List Asset TypesRetrieves all asset types.
- List Audit TrailsRetrieves a list of audit trails from the service.
- List Authorized AccountsRetrieves all authorized accounts.
- List Authorized SitesRetrieves all authorized sites.
- List ExploitabilitiesRetrieves all exploitabilities.
- List Exposed ReportsRetrieves all exposed reports.
- List ScanningRetrieves information about your discovery sources.
- List Scanning TasksRetrieves scanning task information.
- List Site InstallationsRetrieves all installations linked to a site.
- List SoftwareRetrieves a list of paginated software with filters.
- List VulnerabilitiesRetrieves all vulnerabilities.
- Make an API CallPerforms an arbitrary authorized API call.
- Request a ScanRequests a scan for specified documents or files.
- Update an Asset ResourceUpdates an asset resource.
- Watch Audit TrailsTriggers when audit trails are recorded.
- Watch Authorized AccountsTriggers when an authorized account is watched.
- Watch EventsTriggers when a new event occurs.
- Watch ExploitabilityTriggers when exploitability data is updated or available.
- Watch ScansTriggers when a new scan is performed.
- Watch Site InstallationsTriggers when a site's installation is created or updated.
- Watch SoftwareTriggers when new software is added or updated.
- Watch VulnerabilitiesTriggers when new vulnerabilities are detected.
Frequently asked questions
Common questions about connecting Currents and Lansweeper.
Connect your Currents and Lansweeper accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Currents's "Watch Events" fires, WEXTL can "Check an Export Request" in Lansweeper. Currents has 1 trigger (including Watch Events); Lansweeper has 36 actions (including Check an Export Request, Create a Relation, and Create a Scanning Task). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Currents-to-Lansweeper automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Currents (or Lansweeper) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Currents + Lansweeper automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Currents and Lansweeper integration.
- Currents and Lansweeper integration source code, module specs and credentials implementation.
- Our Currents and Lansweeper integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Currents and Lansweeper — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Currents integration information
- Lansweeper integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library