Weavr

GitHub

React to repository events and interact with issues, PRs, and comments.

Triggers

GitHub triggers support two modes: polling (default, uses gh CLI) and webhook (requires public URL).

# Push trigger - react to commits
trigger:
  type: github.push
  with:
    repo: owner/repo
    branch: main           # Optional: filter by branch
    mode: polling          # Default - uses gh CLI locally
    pollInterval: 60       # Poll every 60 seconds

# Pull request trigger
trigger:
  type: github.pull_request
  with:
    repo: owner/repo
    events: [opened, synchronize]

# Issue triggers
trigger:
  type: github.issue.opened
  with:
    repo: owner/repo

trigger:
  type: github.issue.labeled
  with:
    repo: owner/repo
    label: bug             # Optional: filter by label

Trigger Data

GitHub triggers provide rich data you can use in your workflow steps:

Pull Request Trigger Data

# Convenience fields (top-level)
{{ trigger.title }}        # PR title
{{ trigger.body }}         # PR description
{{ trigger.author }}       # PR author username
{{ trigger.url }}          # PR URL
{{ trigger.number }}       # PR number
{{ trigger.action }}       # Event action (opened, synchronize, closed)
{{ trigger.repository }}   # Repository name (owner/repo)

# Files changed
{{ trigger.fileNames }}    # Array of changed file paths
{{ trigger.files }}        # Array of file objects with details

# Full PR object
{{ trigger.pullRequest.title }}
{{ trigger.pullRequest.body }}
{{ trigger.pullRequest.state }}
{{ trigger.pullRequest.head.ref }}   # Source branch
{{ trigger.pullRequest.base.ref }}   # Target branch
{{ trigger.pullRequest.additions }}  # Lines added
{{ trigger.pullRequest.deletions }}  # Lines deleted
{{ trigger.pullRequest.labels }}     # Array of label names
{{ trigger.pullRequest.draft }}      # Is draft PR

Issue Trigger Data

# Convenience fields (top-level)
{{ trigger.title }}        # Issue title
{{ trigger.body }}         # Issue body
{{ trigger.author }}       # Issue author username
{{ trigger.url }}          # Issue URL
{{ trigger.number }}       # Issue number

# Full issue object
{{ trigger.issue.title }}
{{ trigger.issue.body }}
{{ trigger.issue.state }}
{{ trigger.issue.labels }}     # Array of label names
{{ trigger.issue.assignees }}  # Array of assignee usernames
{{ trigger.issue.comments }}   # Comment count

Actions

# Create an issue
- id: create-issue
  action: github.create_issue
  with:
    repo: owner/repo
    title: "New issue from workflow"
    body: "Created by Weavr"
    labels: [automated, triage]

# Add a comment
- id: comment
  action: github.create_comment
  with:
    repo: owner/repo
    issue_number: "{{ trigger.issue.number }}"
    body: "Thanks for reporting!"

# Create a pull request
- id: create-pr
  action: github.create_pr
  with:
    repo: owner/repo
    title: "Automated changes"
    head: feature-branch
    base: main
Local development: Polling mode uses the gh CLI, so you need to have it installed and authenticated (gh auth login).

Telegram

Send messages and receive updates from Telegram bots.

Setup

  1. Create a bot via @BotFather
  2. Set TELEGRAM_BOT_TOKEN environment variable or add to config

Trigger

trigger:
  type: telegram.message
  with:
    chatId: 123456789      # Optional: filter by chat
    chatType: private      # Optional: private, group, supergroup, channel

Actions

# Send a message
- id: notify
  action: telegram.send
  with:
    chatId: "{{ trigger.chatId }}"
    text: "Hello from Weavr!"
    parseMode: HTML        # Optional: HTML, Markdown, MarkdownV2

# Send a photo
- id: send-photo
  action: telegram.sendPhoto
  with:
    chatId: 123456789
    photo: "https://example.com/image.png"
    caption: "Check this out"

Slack

Post messages to Slack channels and respond to events.

Setup

Set SLACK_BOT_TOKEN or SLACK_WEBHOOK_URL.

Actions

# Post to channel
- id: notify
  action: slack.post
  with:
    channel: "#general"
    text: "Deployment complete!"

# Post with blocks
- id: rich-message
  action: slack.post
  with:
    channel: "#alerts"
    blocks:
      - type: section
        text:
          type: mrkdwn
          text: "*Alert:* Service degradation detected"

Discord

Send messages to Discord channels via webhooks.

- id: notify
  action: discord.send
  with:
    webhookUrl: "{{ env.DISCORD_WEBHOOK }}"
    content: "Build completed successfully!"
    username: "Weavr Bot"

Linear

Create and manage Linear issues from workflows.

Setup

Set LINEAR_API_KEY environment variable.

# Create an issue
- id: create-issue
  action: linear.create_issue
  with:
    teamId: "TEAM-123"
    title: "Bug from production"
    description: "{{ trigger.error.message }}"
    priority: 2            # 0=none, 1=urgent, 2=high, 3=medium, 4=low

HTTP / Webhooks

Make HTTP requests and receive webhook events.

Webhook Trigger

trigger:
  type: http.webhook
  with:
    path: /my-webhook      # Available at /webhook/my-webhook

HTTP Request Action

- id: api-call
  action: http.request
  with:
    url: "https://api.example.com/data"
    method: POST
    headers:
      Authorization: "Bearer {{ env.API_TOKEN }}"
      Content-Type: application/json
    body:
      key: value

Email

Send emails via Resend API or SMTP, and receive inbound email webhooks.

Setup

Configure SMTP in ~/.weavr/config.yaml or set environment variables:

email:
  smtp:
    host: smtp.example.com
    port: 587
    secure: false
    user: your-email@example.com
    pass: your-password
    authMethod: login
Environment variables: SMTP_HOST, SMTP_PORT, SMTP_SECURE, SMTP_USER, SMTP_PASS, SMTP_AUTH_METHOD, EMAIL_API_KEY or RESEND_API_KEY, EMAIL_FROM

Send Email

- id: send-email
  action: email.send
  with:
    to: recipient@example.com
    subject: "Workflow Complete"
    text: "Your workflow finished successfully."
    provider: smtp  # auto | smtp | api

Inbound Email Webhook

Configure your email provider to POST inbound email payloads to /webhook/email (or a custom path).

trigger:
  type: email.inbound
  with:
    path: email
    provider: generic

Calendar

Integrate CalDAV calendars (Nextcloud, iCloud, Fastmail, and more).

List Events

- id: list-events
  action: calendar.list_events
  with:
    calendarUrl: "https://cal.example.com/dav/calendars/user/default/"
    username: "user@example.com"
    password: "app-password"
    from: "2026-02-07T00:00:00Z"
    to: "2026-02-14T00:00:00Z"

Create Event

- id: create-event
  action: calendar.create_event
  with:
    calendarUrl: "https://cal.example.com/dav/calendars/user/default/"
    username: "user@example.com"
    password: "app-password"
    summary: "Weekly Sync"
    start: "2026-02-10T15:00:00Z"
    end: "2026-02-10T15:30:00Z"

Upcoming Event Trigger

trigger:
  type: calendar.event_upcoming
  with:
    calendarUrl: "https://cal.example.com/dav/calendars/user/default/"
    username: "user@example.com"
    password: "app-password"
    windowMinutes: 60
    pollIntervalSeconds: 60

Cron Schedules

Run workflows on a schedule.

trigger:
  type: cron.schedule
  with:
    expression: "0 9 * * *"    # Every day at 9 AM
    timezone: America/New_York # Optional, defaults to system timezone

# Common patterns:
# "*/15 * * * *"   - Every 15 minutes
# "0 * * * *"      - Every hour
# "0 9 * * 1-5"    - 9 AM on weekdays
# "0 0 1 * *"      - First day of each month

MCP Servers

Model Context Protocol (MCP) servers extend AI agent capabilities with custom tools. Weavr includes a catalog of 20+ pre-configured MCP servers that can be enabled from the UI.

Available MCP Servers

Server Description Tools Provided
filesystem File system operations read_file, write_file, list_directory, search_files
git Git repository operations git_status, git_diff, git_commit, git_log
github GitHub API access create_issue, create_pr, search_repos, get_file_contents
postgres PostgreSQL database query, describe_table, list_tables
sqlite SQLite database query, describe_table, list_tables
puppeteer Browser automation navigate, screenshot, click, fill, evaluate
brave-search Web search via Brave brave_web_search, brave_local_search
slack Slack workspace access list_channels, post_message, search_messages
google-drive Google Drive access search_files, read_file, create_file
sequential-thinking Step-by-step reasoning sequentialthinking

Enabling via UI

The easiest way to enable MCP servers is through the Settings page in the web UI:

  1. Go to Settings in the web app
  2. Scroll to the MCP Servers section
  3. Click the toggle to enable/disable servers
  4. Servers start/stop immediately - no restart required

Configuration via YAML

You can also configure MCP servers in ~/.weavr/config.yaml: 

mcp:
  servers:
    filesystem:
      command: npx
      args: [-y, "@modelcontextprotocol/server-filesystem", "/path/to/dir"]

    github:
      command: npx
      args: [-y, "@modelcontextprotocol/server-github"]
      env:
        GITHUB_PERSONAL_ACCESS_TOKEN: "your-token"

    postgres:
      command: npx
      args: [-y, "@modelcontextprotocol/server-postgres"]
      env:
        DATABASE_URL: "postgresql://user:pass@localhost/db"

Using MCP Tools in Workflows

Once enabled, MCP tools are automatically available to AI agents. You can specify which tools to use in the tools field: 

steps:
  - id: analyze-repo
    action: ai.agent
    with:
      task: "List all TODO comments in the repository"
      tools:
        - git_status          # From git MCP
        - search_files        # From filesystem MCP
        - read_file           # Built-in or MCP
Tool discovery: The Workflow Builder shows all available tools (built-in + MCP) when editing an AI agent step. Tools from MCP servers are labeled with their server name.