OpenClaw

sensorpro

Manage your Sensorpro email marketing account in OpenClaw.

forcequit0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install forcequit/sensorpro

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Use this skill to manage your Sensorpro email marketing account in OpenClaw.

Official docs:

Home: https://sensorpro.net/api/
Contacts: https://sensorpro.net/api/contacts.html
Campaigns + metrics: https://sensorpro.net/api/campaigns.html
Relay Email: https://sensorpro.net/api/sendemail.html
Imports: https://www.sensorpro.net/api/imports.html
Account: https://sensorpro.net/api/account.html

Setup (required)

Set these environment variables in your OpenClaw .env (or in the shell before running curl):

SENSORPRO_API_KEY — API key for the x-apikey header
SENSORPRO_ORG — organization code/name
SENSORPRO_USER — API username (must be an API user)
SENSORPRO_PASS — API user password

How to get the API key

From the Sensorpro UI:

Go to API → API keys
Select “Sensorpro rest API default key”
Copy the key value into SENSORPRO_API_KEY
If your API key is IP-restricted, whitelist the calling IP (the machine running OpenClaw)

The key is passed as an HTTP header:

x-apikey: $SENSORPRO_API_KEY

How to create an API user

Sensorpro distinguishes between UI users and API users:

API users have no UI access but can use the REST API.
Normal users have UI access but typically cannot use the REST API.

Create a dedicated API user in Sensorpro and set:

SENSORPRO_USER to that username
SENSORPRO_PASS to that password

Safe secret handling (important)

Put secrets in ~/.openclaw/.env (or your process manager), not in SKILL.md.
Don’t commit .env to git.
Rotate the API key if it’s ever pasted into a public place.

Global gotchas

IP allowlisting: Sensorpro REST API can be locked to whitelisted IPs.
Every response includes Result.TotalErrors; treat 0 as success.
Signin token (Token) must be used in the URL path for most endpoints.
Logoff: server may require a body (HTTP 411 otherwise). Use -d '{}'.

Quick workflow pattern (recommended)...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/forcequit/sensorpro
Version: —
Commit: 50cf00acd86484cf6cac8e22059a28c817408aff
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

Use this skill to **manage your Sensorpro email marketing account in OpenClaw**.

Official docs:
- Home: https://sensorpro.net/api/
- Contacts: https://sensorpro.net/api/contacts.html
- Campaigns + metrics: https://sensorpro.net/api/campaigns.html
- Relay Email: https://sensorpro.net/api/sendemail.html
- Imports: https://www.sensorpro.net/api/imports.html
- Account: https://sensorpro.net/api/account.html

## Setup (required)
Set these environment variables in your OpenClaw `.env` (or in the shell before running curl):

- `SENSORPRO_API_KEY` — API key for the `x-apikey` header
- `SENSORPRO_ORG` — organization code/name
- `SENSORPRO_USER` — API username (**must be an API user**)
- `SENSORPRO_PASS` — API user password

### How to get the API key
From the Sensorpro UI:
1) Go to **API → API keys**
2) Select **“Sensorpro rest API default key”**
3) Copy the key value into `SENSORPRO_API_KEY`
4) If your API key is IP-restricted, whitelist the **calling IP** (the machine running OpenClaw)

The key is passed as an HTTP header:
- `x-apikey: $SENSORPRO_API_KEY`

### How to create an API user
Sensorpro distinguishes between UI users and API users:
- **API users** have *no UI access* but **can** use the REST API.
- **Normal users** have UI access but typically **cannot** use the REST API.

Create a dedicated **API user** in Sensorpro and set:
- `SENSORPRO_USER` to that username
- `SENSORPRO_PASS` to that password

### Safe secret handling (important)
- Put secrets in `~/.openclaw/.env` (or your process manager), **not** in `SKILL.md`.
- Don’t commit `.env` to git.
- Rotate the API key if it’s ever pasted into a public place.

## Global gotchas
- **IP allowlisting**: Sensorpro REST API can be locked to whitelisted IPs.
- Every response includes `Result.TotalErrors`; treat `0` as success.
- **Signin token** (`Token`) must be used in the URL path for most endpoints.
- **Logoff**: server may require a body (HTTP 411 otherwise). Use `-d '{}'`.

## Quick workflow pattern (recommended)...

搜索