Omnisend
ReviewAudited by ClawScan on May 17, 2026.
Overview
The skill is a coherent Omnisend integration via ClawLink, but users should understand it depends on an external plugin/service that can access and change marketing account data after connection.
Before installing, make sure you trust ClawLink and the ClawHub plugin source, connect only the Omnisend account you intend to use, and carefully review any preview before approving contact changes, imports, automation edits, or campaign sends.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The user must trust the separately installed ClawLink plugin for the integration to work.
The skill is instruction-only but depends on installing a separate ClawLink plugin that is not included in the reviewed artifacts.
Install the verified ClawLink plugin: `openclaw plugins install clawhub:clawlink-plugin`
Install the plugin only from the expected ClawHub source and review ClawLink's documentation/source if you need stronger assurance.
Once connected, the integration may access Omnisend data and perform actions allowed by the user's granted Omnisend permissions.
The integration delegates Omnisend credential and account access to ClawLink, which is expected for the stated purpose but grants meaningful account authority.
ClawLink ... handles hosted connection flows and credentials so you don't need to configure Omnisend API access yourself.
Connect only the intended Omnisend account, review granted permissions, and revoke the ClawLink connection if it is no longer needed.
A mistaken confirmation could change contacts, imports, campaigns, or audience targeting in Omnisend.
The skill can perform high-impact marketing operations, but it explicitly requires confirmation before broad or external-facing writes.
Confirm before sends, imports, or broad audience changes
Review previews carefully before approving sends, imports, automation changes, or broad audience updates.
Credential and integration activity is mediated by ClawLink rather than only local OpenClaw state.
The skill discloses a local-to-ClawLink credential flow and uses ClawLink as the gateway for Omnisend tooling.
The resulting device credential is stored locally in OpenClaw's plugin config and is only sent to `claw-link.dev`.
Use this skill only if you are comfortable with ClawLink handling the Omnisend connection, and do not paste raw credentials into chat.