What makes Cold Email Campaigns with SalesBlink notable?

1.2K downloads. Trust evidence available

How should Cold Email Campaigns with SalesBlink be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Cold Email Campaigns with SalesBlink

Run cold email sequences on autopilot and manage full sales outreach campaigns via the SalesBlink API. Use this skill to build automated multi-step email cam...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

1.0.9

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.9release · observed May 13, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17adpah8ftb77dvdzgdjdm31n84scpv:cold-email-salesblink

Install using `clawhub skill install s17adpah8ftb77dvdzgdjdm31n84scpv:cold-email-salesblink` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/sheksushant/cold-email-salesblink before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-sheksushant-cold-email-salesblink/snapshot"

Documentation

CLAWHUB

150,864 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: cold-email-salesblink
description: >
  Run cold email sequences on autopilot and manage full sales outreach campaigns via the SalesBlink API.
  Use this skill to build automated multi-step email campaigns (sequences), manage leads and email lists,
  create reusable templates with merge variables and spintax, connect sending accounts (Gmail, Outlook, SMTP),
  handle inbox replies, and track campaign analytics (opens, clicks, replies, sent).
  Also supports bulk contact imports, email deliverability testing (inbox placement / spam checks),
  sender warmup links, workspace/team management, and any HTTP request to the SalesBlink platform.
version: 1.0.0
compatibility: >
  Requires network access to run.salesblink.io and a SALESBLINK_API_KEY.
  Supports any HTTP client (curl, Node.js fetch, Python requests, PowerShell, etc.).
  No prior knowledge of SalesBlink is needed: the skill guides you through connecting email accounts,
  importing leads, writing templates, building sequences, launching campaigns, and monitoring deliverability.
metadata:
  openclaw:
    requires:
      env:
        - SALESBLINK_API_KEY
    primaryEnv: SALESBLINK_API_KEY
---

# SalesBlink Public REST API v1.0.0

## When to use this skill

Use this skill when the user wants to:

- Create, update, or manage email lists, sequences, templates, or senders
- Add, update, move, or remove contacts/leads
- Send or reply to emails via the inbox
- Check campaign analytics (opens, clicks, replies, sent)
- Set up outreach campaigns end-to-end
- Manage workspaces, users, folders, or deliverability tests
- Make any HTTP request to `run.salesblink.io/api/public/v1.0.0`

## Safety & Compliance Guardrails

Before performing any high-risk action, pause and obtain explicit user confirmation. Document the confirmation in your reasoning.

### Sequence launches (ASI02)
- **Always create sequences with `paused: true` first.**
- Before launching (setting `paused: false` or `launchTimingMode: "now"`), show the user:
  - Final recipient list(s) and estimated lead count
  - Sender account(s) that will send the emails
  - Template subject lines and content for every step
  - Schedule / timezone / sending hours
  - Pause state and stop conditions (e.g., `stopWhenReplyRecieved`)
- Only launch after the user explicitly confirms. Do not auto-launch.
- Prefer `paused: true` and let the user resume manually when ready.

### DFY orders and billing (ASI02)
- Treat all DFY domain/mailbox orders and billing actions as **payment-sensitive**.
- Before placing any order, confirm with the user:
  - Exact domain name(s) to purchase or connect
  - Mailbox count, provider (Google / Outlook / Azure), and price
  - Cancellation limits and recurring cost implications
- Do not place DFY orders or manage payment methods unless explicitly requested.

### API key management (ASI03)
- Only use `/keys` endpoints for **explicit credential-administration requests**.
- Before refreshing or deleting a key, confirm:
  - The exac

_meta.json

{
  "ownerId": "kn7fnmjb3nqezc1gc8b74fmgrh84rx5t",
  "slug": "cold-email-salesblink",
  "version": "1.0.9",
  "publishedAt": 1778690646712
}

references/account-config.md

# Account Config — Domains & Signatures

## Domains

**GET** `/domains`

Headers:
- `Authorization`: `SALESBLINK_API_KEY`

List custom tracking domains for the account.

## Signatures

**GET** `/signatures`

Headers:
- `Authorization`: `SALESBLINK_API_KEY`

List email signatures.

> Signature IDs can be referenced when adding senders via the `signature_id` field. You can pass either the signature ID or its name.

references/activity.md

# Activity Tracking

## Endpoints

| Endpoint | Method | Description |
|----------|--------|-------------|
| `/sent` | GET | Log of all sent emails |
| `/opens` | GET | Email open events |
| `/clicks` | GET | Link click events |
| `/replies` | GET | Reply events |

## Query Parameters

All activity endpoints support:

| Param | Type | Description |
|-------|------|-------------|
| `per_page` | integer | Max 100 |
| `page` | integer | 1-indexed |
| `sequence_id` | string | Filter by sequence UUID |
| `recipient_email_address` | string | Filter by email address |
| `since` | integer | Filter events after this timestamp (ms) |
| `from` | integer | Start of date range (timestamp, ms) |
| `to` | integer | End of date range (timestamp, ms) |

> Use `per_page` and `page` for activity endpoints — not `limit`/`skip`.

## Response Format

Each event includes:
```json
{
  "id": "...",
  "time": 1715000000000,
  "message": "Sent",
  "type": "outreach",
  "sequence": "sequence-uuid",
  "email": "[email protected]",
  "sequence_name": "Campaign Name"
}
```

For clicks and replies, `template_name` is also included.

## Examples

**GET** `/opens?sequence_id=SEQ_ID&per_page=100&page=1`

Headers:
- `Authorization`: `SALESBLINK_API_KEY`

**GET** `/replies?since=TIMESTAMP_30_DAYS_AGO&per_page=100`

Headers:
- `Authorization`: `SALESBLINK_API_KEY`

references/api-keys.md

# API Key Management

> **Restricted**: Only use these endpoints for explicit credential-administration requests. Confirm the exact key and impact before refreshing or deleting anything.

## Endpoints

| Endpoint | Method | Description |
|----------|--------|-------------|
| `/keys` | GET | List all API keys for the account |
| `/keys` | POST | Create a new API key |
| `/keys/:id/refresh` | POST | Refresh an existing API key (deletes old, creates new) |
| `/keys/:id` | DELETE | Delete an API key |

## Get API Keys

**GET** `/keys`

Headers:
- `Authorization`: `SALESBLINK_API_KEY`

Returns a list of all API keys associated with the account.

## Create API Key

**POST** `/keys`

Headers:
- `Authorization`: `SALESBLINK_API_KEY`
- `Content-Type`: `application/json`

Body:
```json
{ "name": "Zapier Integration" }
```

| Field | Type | Req | Description |
|-------|------|-----|-------------|
| `name` | string | ✅ | A descriptive name for the API key |

## Refresh API Key

**POST** `/keys/:id/refresh`

Headers:
- `Authorization`: `SALESBLINK_API_KEY`

This endpoint generates a new API key and deletes the old one identified by `:id`. 

> [!WARNING]
> If you refresh the key you are currently using, you must update your integration immediately as the old key will be revoked.

## Delete API Key

**DELETE** `/keys/:id`

Headers:
- `Authorization`: `SALESBLINK_API_KEY`

Deletes the specified API key.

> [!IMPORTANT]
> - You cannot delete the API key you are currently using.
> - At least one API key is required per account. If you want to replace your only key, use the Refresh endpoint instead.

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.