CLI & Agent Skills

What the Trigify CLI is, how to install it, and how to use it from terminal sessions and agent harnesses like Claude Code.

The Trigify CLI is a terminal client for the Trigify API. It's used by technical operators, agent harnesses (Claude Code, custom MCP flows, Codex), and automation pipelines to create searches, fetch results, and drive workflows without touching the dashboard.

Why a CLI?

Trigify exposes the same product surface across REST, MCP, CLI, and Jarvis. The CLI is the right entry point when you want:

  • Scripted or scheduled access from a server or laptop.
  • Agent-driven access from frameworks that prefer terminal tools over raw HTTP.
  • A consistent surface across per-source endpoints — Reddit, X, Substack, Business Network, YouTube, Hacker News, Podcasts, and others as they ship.

Installing the CLI

Install instructions and the latest CLI version are available from Settings → CLI & Agent Skills in the app. That page also lists the agent-skill files you can drop into Claude Code or other harnesses to get Trigify wired in as a first-class tool.

Authentication

  1. Open Settings → API Keys and create or copy an API key.
  2. Set it in your shell environment (e.g. export TRIGIFY_API_KEY=...).
  3. The CLI uses this key for every request. If a request returns 401, the key is missing or invalid; rotate it from the API Keys settings.

What the CLI can do

  • Create, list, get, update, and delete searches — including per-source search endpoints.
  • Fetch results from saved searches.
  • Trigger and inspect workflows.
  • Push custom signals into Trigify for use with the Custom Signals trigger.

Run trigify --help at any time to see the full command list for your installed version.

Using Trigify from agent harnesses

The CLI is the recommended way to expose Trigify to coding agents like Claude Code, Codex, or custom MCP clients. The agent-skill files in Settings → CLI & Agent Skills include preconfigured commands and the conventions Trigify expects for search creation, workflow operation, and signal handling.

MCP vs CLI

If your agent supports MCP natively, you can point it at https://api.trigify.io/mcp instead of going through the CLI. The MCP surface and the CLI cover overlapping territory; pick the one that fits your harness.

Related articles