1What FoxPlug reads from Creem
These are the exact things it reads, and nothing else.
| What | The details it takes |
|---|---|
| Subscriptions | up to 5 pages of 100 subscriptions from the live Creem address. Per subscription: status, the product's price, currency and billing period, created time and cancelled time. |
| Monthly amount per subscription | the product price turned into a monthly figure from the product's billing interval and count, or from its billing period name (every month, three months, six months, year, day). |
| Active subscribers and monthly revenue | subscriptions with status active, trialing or scheduled to cancel are counted as active; trialing ones add nothing to monthly revenue. |
| Past-due subscriptions | status past due or unpaid: how many, and the monthly amount at risk. Stored only when above zero. |
| New and cancelled in 30 days | new = created in the last 30 days; cancelled = status canceled with a cancelled time (or, failing that, an updated time) in the last 30 days. |
| Currency | the currency on the product, in lower case; usd when none is given. |
2Moments it finds, and what each becomes
A moment is one thing that happened in Creem worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.
The first active subscription is read
The moment is titled like this: 💸 Got the first paying customer
A maker connects Creem and presses Check for what's new. One subscription is active, so the moment reads 'Got the first paying customer' with the line 'Someone is paying for the thing I'm building (counted from Creem).' A post is drafted for review.
Active subscriptions reach 10, 50 or 100
The moment is titled like this: Passed 10 paying subscribers
The 10th active subscription is read. The moment 'Passed 10 paying subscribers' is written once, described as '10 people now pay for it every month (counted from Creem).'
One or more subscriptions are past due
The moment is titled like this: No milestone. Brief line like '2 subscriptions are past due, $48 a month at risk.'
Two subscriptions show past due. The monthly amount at risk is added up from their prices and the brief puts a Fix line ahead of any post.
Monthly revenue crosses a milestone number between two reads
The moment is titled like this: Brief line: 'You passed $500 a month. Tell people.'
A first read shows $480 a month and a later read at least a day on shows $520. The brief offers a Say line for crossing $500.
3How the brain uses it
The rules below are the ones that apply to Creem. The same rules, with worked examples, are on the brain page.
- Creem reports past-due subscriptions, which become the fix line. How the brain decides
- The first paying customer, then 10, 50 and 100 subscribers, become say lines. How the brain decides
- Crossing a monthly revenue milestone ($100 up to $50,000) becomes a Say line. How the brain decides
- Card expiry, saving customers and win-back need each customer's details, so they stay Stripe only. How the brain decides
- When several revenue tools are connected the brief uses one: connected Stripe first, else another connected one. How the brain decides
4Set up Creem in a few steps
Access: Production API key pasted into FoxPlug. What to give it: Production API key from the Developers page. Creem's docs describe no read-only or limited key, so the guide does not claim one.
- In Creem, switch Test Mode off (bottom of the left menu) and open Developers.
- Copy the API Key shown for production.
- Paste it into the Creem box in FoxPlug. Keep it private; FoxPlug only reads and never writes.
5Limits worth knowing
Where it stops, so nothing surprises you.
- At most 500 subscriptions are read (5 pages of 100); if more remain the result is marked partial.
- When a subscription carries only a product id and not the product itself, its price is unknown: it still counts as active but adds 0, and the result is marked partial.
- A subscription scheduled to cancel still counts as active until it ends.
- Creem does not offer a read-only key, so the key pasted can do more than FoxPlug asks of it; the code only sends GET reads.
- The test-key check on the key's first letters is a best guess; Creem's docs do not state the prefix. The live address refuses a test key anyway.
- No discount adjustment: the product price is used as listed.
- If subscriptions use more than one currency, the last currency seen is reported for the whole total and amounts are not converted.
- The brief shows one revenue tool at a time, so with Stripe connected as well, these numbers are not the ones shown.
- No failed-payment rescue, expiring card, saving or win-back drafts: those are Stripe only.
6What it never reads
Read only means read only, and the list below is what the code leaves alone.
- Customer names and emails. The customer part of each subscription is never touched.
- Discounts, tax and payments: only the product price is used.
- Anything written back: only plain GET reads of the subscription list.
- Test data: a key starting creem test is refused, and any subscription marked as test or sandbox is skipped.
7How Creem differs from the tools next to it
Creem puts the price on the product inside each subscription, so no second lookup is needed, unlike Lemon Squeezy. Unlike Dodo Payments and Whop it has no limited-permission key, so the guide does not say read-only. It pages by number like Polar.
8Questions
Does FoxPlug see my customers' names or emails from Creem?
No. It reads subscription status, product price, currency, billing period and dates. No customer detail is read or stored.
Is the Creem key read-only?
No. Creem's documentation describes only one API key per mode, with no read-only option. FoxPlug sends only read requests, but keep the key private.
Can I use a test key?
No. A test key holds test data, so FoxPlug refuses it and asks for the production key.
When does it read Creem?
When you press Check for what's new or Build the brief.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.