Integration
Connect PostHog to Intelliprint
When something happens in PostHog, your agent does the next thing in Intelliprint. Describe it in plain language and the automation is built, tested on every branch and kept running.
Build it
What do you want PostHog and Intelliprint to do together?
Describe it and your agent reads both APIs, builds the automation, tests every branch and ships it. The list below is what exists today, not the limit.
Ask the assistant
You'll sign in before anything runs. What you typed comes with you.
Or work from Claude Code
Install the APIANT plugin for Claude Code and build, edit, test and read run history from your terminal. Every plan gets this, including free, and it spends no assistant credits.
Connect Claude CodeEverything your agent can do with PostHog and Intelliprint
Triggers and actions 1 trigger ยท 25 actions
Trigger
Action PerformedTriggers when an action is performed by a user.
Action
Add annotationCreate a new annotation on the project timeline (content, date_marker, scope). POST /api/projects/:project_id/annotations/
Action
Capture EventCaptures an event.
Action
Evaluate feature flagsEvaluate all feature flag values for a given distinct_id/person, returning flag states for use in automation branching. Public POST /flags endpoint (project token auth).
Action
Get personRetrieve a single person by ID. GET /api/projects/:project_id/persons/:id/
Action
List annotationsList annotations in the project. GET /api/projects/:project_id/annotations/
Action
List cohortsList cohorts defined in the project. GET /api/projects/:project_id/cohorts/
Action
List feature flagsList feature flags defined in the project. GET /api/projects/:project_id/feature_flags/
Action
List insightsList saved insights (charts/graphs) in the project. GET /api/projects/:project_id/insights/
Action
List personsList/search persons in the project, optionally filtered by distinct_id or properties. GET /api/projects/:project_id/persons/
Action
Update personUpdate a person's properties by ID. PATCH /api/projects/:project_id/persons/:id/
Action
Add backgroundCreate a background/letterhead used for print jobs. POST /backgrounds
Action
Add mailing listCreate a mailing list. POST /mailing_lists
Action
Add recipientCreate a recipient in a mailing list. POST /mailing_lists/{mailing_list}/recipients
Action
Delete mailing listDelete a mailing list. DELETE /mailing_lists/{id}
Action
Delete print jobDelete or cancel a print job. DELETE /prints/{id}
Action
Delete recipientDelete a mailing list recipient. DELETE /mailing_lists/{mailing_list}/recipients/{id}
Action
Get mailing listRetrieve a mailing list by id. GET /mailing_lists/{id}
Action
Get print jobRetrieve a single print job by id. GET /prints/{id}
Action
Get recipientRetrieve a mailing list recipient by id. GET /mailing_lists/{mailing_list}/recipients/{id}
Action
List mailing listsList all mailing lists. GET /mailing_lists
Action
List recipientsList all recipients in a mailing list. GET /mailing_lists/{mailing_list}/recipients
Action
Send LetterWe'll print and mail out any content you provide us as a letter.
Action
Update mailing listUpdate a mailing list. POST /mailing_lists/{id}
Action
Update print jobUpdate an existing print job. POST /prints/{id}
Action
Update recipientUpdate a mailing list recipient. POST /mailing_lists/{mailing_list}/recipients/{id}
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.