GitHub Integration (PAT)

Use a GitHub Personal Access Token (PAT) to enable workflow nodes that create issues.

Security

• Tokens are stored per user in integration_configs.
• They are read only at execution time when a github node runs.
• The raw token is never returned by HTTP APIs (the save response may include tokenLastFour for UI confirmation only).

Steps

1. Create a PAT in GitHub:
   • Scope: repo (or public_repo for public repos only), or a fine-grained token with Issues write on the target repository.
2. Go to Dashboard → Integrations.
3. Paste the token (minimum 20 characters per API contract).
4. Optionally set a default repository: owner/repo (required for nodes that use repository: "__default__").

Using in a workflow

GitHub nodes use type: "github" with params similar to the bundled Verified Incident Response notify step:

{
  "type": "github",
  "params": {
    "repository": "__default__",
    "issueTitle": "High severity alert"
  }
}

• __default__ resolves to the default repository saved on your GitHub integration.
• If issueTitle is omitted, Cascades generates a default title from the run id.

What to expect

• On success

  • An issue is created in the repository.
  • Logs include github_issue_created.
  • Issue fields (number, URL, state, title) are included in the task output and therefore in the workflow proof payload.

• If not configured

  • The run logs integration_missing.
  • The task fails deterministically (no external call).

• If the row exists but no token is stored

  • Logs include github_executor_missing_token.

See also Verified Incident Response (demo) and the step-by-step Integration smoke test (recommended order).