Actions57
- 1. Manager Actions
- 2. Mouse Actions
- 3. Keyboard Actions
- 4. Browser Control Actions
- 5. Element Actions
- 6. Image Actions
- 7. Others Actions
- 8. Email Actions
- 9. Developer Actions
- 10. General Debug Actions
1. Manager → Pull_Profile_from_NAS
AI-generatedSummary
Downloads the latest archived profile for the specified GPM Profile ID from the NAS store to the worker and extracts it into a profile-specific subdirectory. By default, it acquires and renews a lease while working; the output includes the destination directory and additional arguments derived from config.json.
Inputs
- Topic (required) — MQTT topic used to send the request to the client.
- Profile ID (required) — GPM profile identifier to pull from the NAS store.
- QoS — MQTT delivery quality level; defaults to 1 (at least once).
- Include Input Items — Optionally attach selected fields from incoming items to payload.inputItems. Off by default; choose fields with Include Input Fields.
- Wait For Response — Whether to wait for the client's MQTT response before returning; defaults to false. Response Timeout is available when enabled.
- Response Timeout (sec) — Maximum wait for a response, in seconds; defaults to 60.
- Delay Next Step (ms) — Delay before continuing after publish, or after receiving a response when waiting. Defaults to rand(200,1000).
- Dest Dir — Worker-side root directory for extracted profiles. If omitted, the operation uses LOTUS_GPM_PROFILE_DIR.
- Acquire Lease — Acquire and heartbeat-renew a lease before downloading; defaults to true. Disable to read without acquiring a lease.
- Host (lease/audit) — Optional host value for lease or audit metadata.
- Lease TTL (sec) — Optional lease time-to-live in seconds.
- Store (UNC/mount) — Optional NAS store path or mount override.
Output shape
A client response containing the destination directory and additional arguments derived from config.json when the client completes the pull.
The operation sends an MQTT request. With Wait For Response off, it proceeds after publishing; with it on, it waits up to the configured timeout. The source excerpt provides signatures rather than implementation bodies, so additional response fields and error behavior are unspecified.