DashboardSign inStart your trial

PostHogPostHog
01Integration field card

PostHog Automation, Approvals, Workflow Integration

Run PostHog on autopilot. Keep the veto.

520 actions11 triggers

AI can bulk delete persons and feature flags, assign roles, and archive survey data in PostHog. Rills queues each action for approval before it runs.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential analytics action from PostHog arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue (3)

POSTHOG · FLAG CLEANUP
1 / 3

Delete 7 feature flags unused for 30 days?

7 flags · last used >30 days ago

No active experiments referencing them

Same pattern as Q1 cleanup

90%
SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, and no surprise send you find out about after it's already out the door.

  3. Clear runs stop waiting on you.

    Every run is scored against your review step. The ones that clearly match your judgment run above your threshold without a tap; the borderline ones still come to the queue. Autonomy is earned run by run, never switched on for good.

03. Overview

About PostHog automation

A bulk-delete of feature flags fires during a product launch because nobody checked the schedule first. The fallout hits your team’s Slack before you even see the change.

When PostHog runs unsupervised

PostHog actions that should be routine can break things fast when no one is watching. A single misconfigured change ships, and the only evidence is a support ticket spike.

  • Adding a person to a static cohort: the wrong segment gets dropped into a campaign trigger, and emails go to people who never should have received them.
  • Creating project insights with customizable parameters: a misconfigured date range makes it look like churn spiked, sending the team into a panic.
  • Bulk-deleting feature flags: a flag that’s still controlling a live experiment gets removed, breaking the experiment for everyone.
  • Adding a dashboard collaborator with full access: a contractor sees financial data they shouldn’t have.

What Rills does inside PostHog

Rills handles PostHog automation by queuing every proposed change before it executes. It can prepare adding collaborators, creating cohorts, or deleting feature flags, but it waits for your call. For teams using PostHog as a lightweight CRM for product-qualified leads, that means cohort lists or insight shares never go out until you’ve seen them.

The action queues up. You approve from your phone, or you don’t. Nothing ships until you decide.

Why PostHog has no triggers and how Rills fills the gap

PostHog doesn’t send events to kick off workflows. So there’s no built-in way to react when a new insight is saved or a cohort changes. Rills fills the gap with scheduled checks and context from upstream tools, surfacing the right moment to act.

  • Feature flags: periodic scan for flags unused in the last 30 days, proposing a bulk delete for your review.
  • Static cohorts: when a new static cohort is created manually or via another tool, Rills suggests adding the right persons based on the last web event.
  • Dashboard collaborator access: nightly check of access levels, flagging anyone with edit permissions who shouldn’t have them.
  • Project insights: when a new project insight is created, propose a review of the parameters before it’s shared with the team.
04. Triggers

What wakes Rills up in PostHog

When these events fire, Rills proposes the next move and waits for your call.

  • webhook

    POSTHOG ACTION PERFORMED

    Triggers when an event matches one of the saved PostHog Actions you configure. Use this instead of Event Captured when the behaviour you care about spans several event names or element matches, and you want PostHog's Action definition to stay the single place it is described. Deliveries count toward your PostHog data pipelines usage, so it pays to watch just the Actions you act on.

  • webhook

    POSTHOG ACTIVITY LOG ENTRY CREATED

    Triggers when PostHog records an activity-log entry for the project — any audited change to a feature flag, insight, dashboard, destination, experiment or survey. This is the whole audit stream, so it is high volume; branch on `scope` and `activity` for the changes you care about.

  • webhook

    POSTHOG EARLY ACCESS FEATURE UPDATED

    Triggers when an early-access feature changes — most usefully when it moves between stages, such as concept to beta to general availability. The payload carries the whole feature both before and after, so compare `previous` with `next` to see what moved.

  • webhook

    POSTHOG ERROR TRACKING ISSUES MERGED

    Triggers when two or more error-tracking issues are merged into one. The payload is the surviving issue; `merged_issue_ids` names the ones that were absorbed, so anything you track against those ids should be repointed.

  • webhook

    POSTHOG ERROR TRACKING ISSUE ASSIGNED

    Triggers when an error-tracking issue is assigned to a user, a group or a role. Reassigning an already-assigned issue fires it again; clearing an assignee fires Error Tracking Issue Unassigned instead.

  • webhook

    POSTHOG ERROR TRACKING ISSUE CREATED

    Triggers when PostHog groups an exception into an error-tracking issue it has never seen before. Fires once per issue, on the first occurrence — later occurrences of the same fingerprint do not fire it.

05. Actions

What Rills can do in PostHog

6 of 520 actions across reads, writes, and updates.

  1. 01

    Get Hog function metric totals

    Read aggregate execution metric totals for a PostHog Hog function.

  2. 02

    Get billing details

    Retrieve billing and subscription details for the connected PostHog account.

  3. 03

    Get error tracking issue

    Retrieve one error tracking issue by ID for a PostHog project.

  4. 04

    Get external data schema

    Retrieve one external data schema and its sync configuration.

  5. 05

    Get spike detection configuration

    Retrieve the active error tracking spike detection configuration for a project.

  6. 06

    List error tracking issues

    List a project's error-tracking issues with offset pagination.

06. FAQ

Common questions about PostHog automation

Can I get mobile approvals before deleting PostHog feature flags?

Yes. Rills queues every bulk feature flag deletion and waits for your swipe. You review the list from your phone: which flags are still in use, which experiments are live. AI proposes the cleanup, you approve before anything ships. No more discovering a critical flag got deleted while you were away.

How is Rills different from Zapier for PostHog automation?

Zapier executes actions the moment a trigger fires. Rills lets AI propose changes to your PostHog project, then holds them in a mobile approval queue. You approve or dismiss from your phone. Approvals and logic are free; you only pay when a real action, like adding a dashboard collaborator, actually runs.

Why use Rills instead of Make for PostHog?

Make runs scenarios without a human check. Rills makes you the final decision‑maker. AI might suggest adding a member to your PostHog org with a specific role, but you approve it from your phone before the invitation goes out. That way, no one gets admin access you didn’t intend.

Does Rills support PostHog webhooks to trigger actions?

Rills can react to signals you define, like an alert that a dashboard hit a metric threshold, and propose a follow‑up action: add a collaborator, create an insight, or delete stale flags. But every proposal waits for your approval before it touches your PostHog project. No webhook event ships unsupervised.

How much does Rills cost for PostHog automation?

Approvals and workflow logic are totally free. You only pay when Rills performs a real action, like calling the PostHog API to add a collaborator, delete feature flags, or create an insight. Each action costs a small amount, with no monthly base fee. You’re never charged for the decisions you review and reject.

How do I automate adding collaborators to PostHog dashboards without losing control?

Rills proposes the access level and collaborator details, then sends the request to your phone. You swipe to approve before the dashboard is shared. That way, you never accidentally give view‑only access to someone who needed full edit rights, or expose revenue data to a team member who shouldn’t see it.

How do I automate PostHog insight creation with AI still letting me review?

AI drafts the insight parameters based on the patterns it sees, then presents the proposal in your mobile queue. You review the charts, filters, and breakdowns, and approve from your phone before it’s saved to the project. You keep the final say on what gets added to your analytics.

Can I automate adding members to a PostHog organization with role approval?

Yes. Rills lets AI propose adding a member to your PostHog organization with a specific role, but the invitation waits for your approval. You review the name, email, and role from your phone before it ships. That prevents accidental admin grants or adding someone to the wrong project.

07. NEXT MOVE

Approve every PostHog change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.