Skip to main content
An action is one exact change the Co-founder prepared for you. This page lists every action type. For how the queue, approvals and automation work, see Actions and approvals. The Type column is the value you see in the API (action_type), in Settings → Automation → Policy rules and in autoApproveTypes.

Summary

“Automatic” means the action can run without your approval. This is only possible in write mode. In read mode every action waits for you.
A metadata update that would drop a search term you rank in the top 20 for is never applied automatically, at any autopilot level. A policy rule set to Require approval also overrides every “automatic” case above.

Store

App Store metadata update

asc_metadata_update

Review reply

asc_review_reply The Co-founder only proposes replies for real, unanswered reviews. A proposal for a review that was already answered is dropped before it reaches your queue.

New App Store version

asc_version_create

Google Play listing update

google_play_metadata_update

Team tools

Linear issue and GitHub issue

linear_issue, github_issue

Notion page

notion_page

Webhook post

webhook_post

Coding agent task

engineering_delegate

Ads

All ads actions always need your approval.

Apple Ads campaign change

asa_campaign_update

Apple Ads keyword bid

asa_keyword_bid_update

Apple Ads negative keywords

asa_add_negative_keywords

Meta Ads campaign change

meta_campaign_update

TikTok Ads campaign change

tiktok_campaign_update

Revenue and retention

Monetization change

revenuecat_experiment

Win-back campaign

lifecycle_campaign

Content and social

UGC clip

ugc_clip

Social comment reply

social_comment_reply

Automatic retries

When you approve an action and applying it fails, it stays in Approved. Some types are retried for you, about once an hour, up to three attempts in total and for up to 14 days:
  • Review reply
  • Apple Ads campaign change, keyword bid and negative keywords
  • Linear issue, GitHub issue, Notion page
Other types are never retried automatically, because a second attempt could do harm: metadata updates, new versions and coding agent tasks. Use Retry on the card for those. A failure that needs you is never retried: a disconnected integration, a missing permission, an expired token or a missing repository. Fix the connection in Integrations, then retry.