activepieces-1-basic-flow-structure
Sub-skill of activepieces: 1. Basic Flow Structure.
Best use case
activepieces-1-basic-flow-structure is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Sub-skill of activepieces: 1. Basic Flow Structure.
Teams using activepieces-1-basic-flow-structure should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/1-basic-flow-structure/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How activepieces-1-basic-flow-structure Compares
| Feature / Agent | activepieces-1-basic-flow-structure | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Sub-skill of activepieces: 1. Basic Flow Structure.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 1. Basic Flow Structure
## 1. Basic Flow Structure
```typescript
// Flow definition structure
interface Flow {
id: string;
projectId: string;
folderId?: string;
status: 'ENABLED' | 'DISABLED';
schedule?: {
cronExpression: string;
timezone: string;
};
trigger: Trigger;
steps: Step[];
}
// Example flow JSON
const basicFlow = {
"displayName": "New Customer Onboarding",
"trigger": {
"name": "webhook",
"type": "WEBHOOK",
"settings": {
"inputUiInfo": {}
},
"valid": true,
"displayName": "Webhook Trigger"
},
"steps": [
{
"name": "validate_data",
"type": "CODE",
"settings": {
"input": {
"customer": "{{trigger.body.customer}}"
},
"sourceCode": {
"code": "export const code = async (inputs) => {\n const { customer } = inputs;\n \n if (!customer.email || !customer.name) {\n throw new Error('Missing required fields');\n }\n \n return {\n valid: true,\n customer: {\n ...customer,\n email: customer.email.toLowerCase().trim(),\n created_at: new Date().toISOString()\n }\n };\n};"
}
},
"displayName": "Validate Customer Data"
},
{
"name": "create_crm_contact",
"type": "PIECE",
"settings": {
"pieceName": "@activepieces/piece-hubspot",
"pieceVersion": "~0.5.0",
"actionName": "create_contact",
"input": {
"email": "{{validate_data.customer.email}}",
"firstName": "{{validate_data.customer.name.split(' ')[0]}}",
"lastName": "{{validate_data.customer.name.split(' ').slice(1).join(' ')}}",
"properties": {
"source": "activepieces_onboarding",
"created_via": "automation"
}
}
},
"displayName": "Create HubSpot Contact"
},
{
"name": "send_welcome_email",
"type": "PIECE",
"settings": {
"pieceName": "@activepieces/piece-sendgrid",
"pieceVersion": "~0.3.0",
"actionName": "send_email",
"input": {
"to": "{{validate_data.customer.email}}",
"subject": "Welcome to Our Platform!",
"html": "<h1>Welcome, {{validate_data.customer.name}}!</h1><p>We're excited to have you on board.</p>"
}
},
"displayName": "Send Welcome Email"
},
{
"name": "notify_team",
"type": "PIECE",
"settings": {
"pieceName": "@activepieces/piece-slack",
"pieceVersion": "~0.6.0",
"actionName": "send_message",
"input": {
"channel": "#new-customers",
"text": "New customer onboarded: {{validate_data.customer.name}} ({{validate_data.customer.email}})"
}
},
"displayName": "Notify Sales Team"
}
]
};
```Related Skills
digitalmodel-orcawave-orcaflex-proof-workflows
Class-level digitalmodel OrcaWave/OrcaFlex readiness, semantic-proof, fixture-proof, and closeout workflows.
repo-structure
Canonical source layout, test mirroring, root cleanliness, gitignore, docs classification, and committed artifact rules for all workspace-hub tier-1 repos. Consult before creating directories or files in any submodule.
portable-pattern-verification-workflow
Multi-package implementation with verification strategy for cross-platform configuration hardening
plan-gated-issue-validation-workflow
Systematic validation pattern for plan-approved GitHub issues with pre-existing deliverables
multi-year-tax-filing-verification-workflow
Verify and reconcile complex multi-form tax filings by cross-referencing source documents, identifying data dependencies, and validating line-by-line against authoritative records.
multi-file-tax-reconciliation-workflow
Systematic parallel review and reconciliation of multi-document tax filings with cross-reference validation
metadata-only-wiki-sweep-workflow
Disciplined inventory process for cataloging documents by filename/path without content claims, using parent-centric grouping to prevent stub proliferation
github-issue-structure-for-personal-finance-tracking
Pattern for organizing financial analysis work across multiple repos (data/config vs. logic separation)
freetaxusa-efiling-workflow
Navigate FreeTaxUSA e-filing process through final steps, handling session timeouts and identifying required manual signature steps
financial-site-bypass-workflow
Workflow for accessing restricted financial sites when browser automation is blocked
financial-data-export-workflow
Structured process for exporting and analyzing multi-year brokerage transaction history when browser automation is blocked
cash-basis-tax-reconciliation-workflow
Multi-source document reconciliation to establish authoritative tax basis and complete Form 1120 for C-Corps using cash method