Skip to main content
For advanced use cases, you can define your own trigger workflow instead of using the dashboard. This gives you full control over when and how Pullfrog runs.
Custom triggers bypass the dashboard configuration. You’ll need to manage all trigger conditions directly in your workflow file.

​
When to use manual setup

Use a custom triggers.yml if you:
  • Need trigger conditions the dashboard doesn’t support
  • Want to customize the workflow beyond what the dashboard provides
  • Prefer to manage workflows directly in version control

​
Setup

Create .github/workflows/triggers.yml: 
name: Agent Triggers

on:
  issue_comment:
    types: [created]
  pull_request_review_comment:
    types: [created]
  issues:
    types: [opened, assigned]
  pull_request_review:
    types: [submitted]
  # add other triggers as needed

jobs:
  pullfrog:
    # only run if @pullfrog is mentioned
    if: contains(github.event.comment.body, '@pullfrog') || contains(github.event.issue.body, '@pullfrog')
    
    permissions:
      id-token: write
      contents: write
      issues: write
      pull-requests: write
      actions: read
      checks: read
    uses: ./.github/workflows/pullfrog.yml
    with:
      prompt: ${{ toJSON(github.event) }}
    secrets: inherit
This workflow listens for GitHub events and calls pullfrog.yml with the full event payload. Customize the on: block and if: condition to match your needs.

​
Passing event context

The prompt input uses ${{ toJSON(github.event) }} to pass the full GitHub event payload to Pullfrog. This gives the agent access to all context from the triggering event—issue data, PR data, comment content, author info, etc.

​
Required permissions

PermissionPurpose
id-token: writeAuthentication with Pullfrog
contents: writeCreate branches and commits
issues: writeCreate and update issues
pull-requests: writeCreate and update PRs
actions: readRead workflow status
checks: readRead CI check results
Make sure your repository settings allow these permissions for GitHub Actions.