2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill sensorpro- _meta.json807 B
- SKILL.md6.4 KB
Overview
This skill is a practical playbook for calling the Sensorpro REST API from OpenClaw. It provides curl-based patterns, signin/logoff handling, and ready-made endpoint examples for contacts, campaigns, metrics, imports, and relay email. Use it to automate adding/updating contacts, running imports, sending one-off emails, and fetching campaign metrics.
How this skill works
The skill performs three core steps: sign in to obtain a Token, call Sensorpro endpoints with that Token and the x-apikey header, and log off when finished. It includes helper scripts that wrap signin/logoff and let you call any Sensorpro endpoint with a JSON body. Responses include Result.TotalErrors (0 indicates success) and many endpoints require the Token in the URL path.
When to use it
- Integrating Sensorpro with OpenClaw to add or update contact records.
- Automating campaign creation, broadcasting, or querying campaign results (opens, clicks, bounces).
- Running imports (FTP imports, import status checks, clearing tag lists).
- Sending one-off relay emails from a system process or automation.
- Performing account-level tasks like adding sub-organizations or API users.
Best practices
- Store SENSORPRO_API_KEY, SENSORPRO_ORG, SENSORPRO_USER, SENSORPRO_PASS in a secure .env or secrets manager; never commit secrets.
- Follow the recommended workflow: signin once, run calls, logoff; use provided scripts to avoid token handling mistakes.
- Check Result.TotalErrors in every response and treat non-zero as a failure to handle explicitly.
- If API key is IP-restricted, whitelist the calling host; be aware of IP allowlisting issues.
- When logging off, send an empty JSON body (e.g., -d '{}') to avoid HTTP 411 errors.
Example use cases
- Add or update subscribers by email using Contact/UpdateAdd to keep lists synchronized with CRM.
- Trigger a marketing broadcast: create campaign/design/segment and call AddBroadcast to send.
- Fetch campaign results and link-level metrics with GetCampaignResults and GetCampaignResultsLinks for reporting.
- Run a scheduled FTP import and poll GetImportStatus until completion, then clear temporary tag lists.
- Send transactional or one-off messages using Email/SendEmail with HTML and plain-text payloads.
FAQ
From the Sensorpro UI: API → API keys → select the default key and copy it into SENSORPRO_API_KEY. If IP-restricted, whitelist the caller IP.
Do I need a special user for the API?
Yes. Create an API user (no UI access) and set SENSORPRO_USER and SENSORPRO_PASS to that account’s credentials.
What indicates a successful API response?
Every response has Result.TotalErrors; a value of 0 indicates success. Always check this field.