keeperhub-keepers-overview

Files (1)

• SKILL.md

SKILL.md (first lines)

# Node Types

## Overview
Documentation for Node Types integration and usage within the KeeperHub ecosystem.

[Nodes](https://docs.keeperhub.com/keepers)

KeeperHub workflows are built from three types of nodes: Triggers, Actions, and Conditions. Each node type serves a specific purpose in your automation.

Triggers determine when your workflow executes. Every workflow must start with a trigger node.

### Scheduled Trigger
Run your workflow at regular intervals.
Configuration:
- Interval selection (every 5 minutes, hourly, daily, weekly, custom cron)
- Timezone settings
Use Cases: Regular balance checks, periodic report generation, scheduled maintenance tasks

### Webhook Trigger
Run your workflow when an external service sends an HTTP request.
Configuration:
- Unique webhook URL (auto-generated)
- Optional authentication headers
Use Cases: Integration with external systems, CI/CD pipelines, third-party alerts

### Event Trigger
Run your workflow when a specific blockchain event is detected.
Configuration:
- Contract address
- Event signature
- Network selection
Use Cases: React to token transfers, smart contract state changes, on-chain activity

### Manual Trigger
Run your workflow only when you click the Run button.
Configuration:
- No additional setup required
Use Cases: Testing, one-time operations, on-demand executions

Actions perform operations in your workflow. Connect multiple actions to create complex automations.

### Web3 Actions
#### Check Balance
Monitor wallet or token balances on any supported network.
Configuration:
- Network (Ethereum Mainnet, Sepolia, etc.)
- Wallet address to monitor
- Token contract (optional, for ERC-20 tokens)
Output: Current balance value for use in conditions

#### Read Contract
Call read-only functions on smart contracts.
Configuration:
- Network and contract address
- Function to call (auto-populated from ABI)
- Function parameters
Output: Function return values

#### Write Contract
Execute state-changing functions on smart contracts.
Configuration:
- Network and contract address
- Function to call
- Function parameters
- Gas settings
Requirements: Funded Para wallet for gas fees

#### Transfer Funds
Send ETH or tokens to another address.
Configuration:
- Network
- Recipient address
- Amount
- Token contract (optional)
Requirements: Funded Para wallet

### Notification Actions
#### Send Email
Send email notifications when workflow conditions are met.
Configuration:
- Connection (email provider)
- Recipient address(es)
- Subject and message content
- Dynamic variables from workflow

#### Send Discord Message
Post messages to Discord channels.
Configuration:
- Connection (Discord webhook)
- Message content
- Dynamic variables from workflow

#### Send Slack Message
Post messages to Slack channels.
Configuration:
- Connection (Slack workspace)
- Channel selection
- Message content

#### Send Telegram Message
Send messages to Telegram chats and channels.
Configuration:
- Connection (Telegram bot token)
- Chat ID (numeric ID or @username)
- Message content
- Parse mode (plain text or MarkdownV2)
Output: Success status, message ID

### Integration Actions
#### Send Webhook
Send HTTP requests to external services.
Configuration:
- URL (HTTPS required)
- HTTP method (GET, POST, etc.)
- Headers
- JSON payload with dynamic variables

Conditions evaluate data from previous nodes and determine which path the workflow takes.

From nickthelegend/keeperhub-skills, MIT.

More from nickthelegend/keeperhub-skills