Install
Use the public npm package:trigify. Verify with:
trigify login
The CLI requires Node.js 20 or newer. See the full installation guide for API key setup, agent skills, and more.
What The CLI Covers
The public CLI is organized around these top-level command groups:| Command | Purpose |
|---|---|
trigify login, logout, whoami | Authentication and account identity |
trigify search | Saved search and monitor management |
trigify workflow | Workflow creation, drafts, publishing, and testing |
trigify integration | Connected integration metadata and health checks |
trigify profile, company, post, discover | LinkedIn profile, company, post, and creator data |
trigify x | X posting and engagement actions |
trigify credits, org, usage | Billing, org, and usage summaries |
Global Options
These options are available at the root command level and can be combined with any subcommand:| Flag | Description |
|---|---|
--base-url <url> | Override the API base URL. Defaults to the API URL baked into the installed build. |
--api-key <key> | Use an API key instead of OAuth credentials for the current invocation. |
-h, --help | Show command help. |
-V, --version | Show the installed CLI version. |
- Local source builds default to
http://localhost:3333 - Staging builds default to
https://trigify-api-staging.up.railway.app - Stable builds default to
https://api.trigify.io
Output Format
CLI commands return JSON by default. Successful commands are wrapped in asuccess envelope:
stderr, for example when OAuth sessions are refreshed or workflow JSON is auto-fixed before validation.