Automation Workflows 0.1.0
ReviewAudited by ClawScan on May 1, 2026.
Overview
This is a coherent instruction-only guide for building no-code automations, with expected notes around OAuth account access, cross-tool data flows, and persistent workflows.
This skill appears safe to install as an instruction-only automation guide. Before following its workflows, review OAuth permissions, start with test data, avoid sending sensitive customer data to unnecessary tools or channels, and monitor automations after turning them on.
Findings (5)
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.
A poorly configured workflow could send emails, create records, or update business systems incorrectly.
The skill describes automations that can perform actions across multiple business tools. This is purpose-aligned, but users should verify each action before enabling it.
Step 1: Add lead to CRM ... Step 2: Send welcome email ... Step 3: Create task ... Step 4: Send me a Slack notification
Use test workflows first, review every trigger/action mapping, and require manual approval for high-impact actions such as invoices, public posts, or customer emails.
Connected automation tools may be able to read or change data in the user’s linked accounts depending on granted scopes.
OAuth account connections are expected for Zapier/Make/n8n workflows, but they delegate access to third-party services.
Connect your account (authenticate via OAuth)
Review OAuth scopes carefully, connect only the accounts needed for the workflow, and revoke unused automations or tokens.
Lead or customer information could be copied into multiple SaaS tools or notification channels.
The example routes lead/customer data through several external services. This is normal for automation workflows but creates data-boundary considerations.
TRIGGER: New form submission on website ... Add lead to CRM ... Send welcome email ... Create task in project management tool ... Send me a Slack notification: "New lead: [Name]"
Avoid sending sensitive fields into broad Slack channels or unnecessary tools, and confirm privacy/compliance requirements for each connected service.
A workflow can keep running on future triggers and may repeat incorrect actions if misconfigured.
The skill instructs users to enable persistent automations. This is the expected purpose, but enabled workflows can continue acting after setup.
Turn on workflow (Zapier calls this "turn on Zap")
Start with limited triggers, enable error notifications, monitor early runs, and know how to pause or disable each workflow.
Users have limited publisher/source context for deciding whether to trust the guidance.
The skill has limited provenance information. Because it is instruction-only with no install spec or code files, this is a minor verification note rather than a concrete execution concern.
Source: unknown; Homepage: none
Verify the publisher if provenance matters, especially before connecting important business accounts to any recommended automation platform.