- Home
- Resources
- Integrations
- NorthStar by GrowthHackers
NorthStar by GrowthHackers Zapier integrationAutomate NorthStar by GrowthHackers with Zapier.
The NorthStar by GrowthHackers Zapier integration has 1 trigger, 1 action and 0 searches. A new card in NorthStar can start a Zap instantly, and ideas collected elsewhere can land in NorthStar as cards. Small scope, but it covers the two moves a growth team repeats.
Verified Trustpilot reviews · AI, automation & growth agency
What the NorthStar by GrowthHackers Zapier integration does
NorthStar by GrowthHackers is the shared workspace where a growth team logs ideas and runs its tests. On Zapier it does two things: it reports each new card the moment it is created, and it lets another tool create a card for you. That is the whole list, and it is enough for the classic idea pipeline.
Three setups come up again and again. An idea inbox: a form, a support tool or a sales note feeds Create Card, so suggestions from outside the growth team stop dying in someone's email. A team heads-up: New Card posts each fresh idea to a chat channel, so people react while it is still a draft. A backlog mirror: New Card adds a row to a spreadsheet the leadership reads, without opening NorthStar to everyone.
What Zapier cannot do here matters as much. There is no search, so a Zap cannot check whether a similar card already exists before adding one. There is no update action either: once a card is created, Zapier cannot change it, move it or close it. And the trigger only reacts to new cards never to a card being edited.
Both directions in one Zap is a trap: a Zap that creates cards and also starts on new cards in the same workspace sets itself off again and again. If you are still weighing tools, our n8n vs Zapier comparison sets the criteria side by side.
Zapier vocabulary in one minute
Seven words are enough for this page. After this, each one keeps the meaning given here.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a new NorthStar card.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, such as creating a card.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's number counts exactly those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself as it happens. New Card is instant.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Connection
- Your NorthStar account linked to Zapier once, then reused by every step that uses NorthStar.
What a NorthStar Zap really costs
NorthStar by GrowthHackers is not a premium app, so it runs on the free plan. The New Card trigger never costs a task; each card that Create Card actually adds costs one.
- New Card trigger0 tasks
- Each card created1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo
The free plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A form that feeds Create Card fits. Add a filter to keep only some submissions, or a second action, and the Zap becomes multi-step, which needs a paid plan. A Create Card that fails is not counted. The interval grid below applies to polling triggers only; New Card is instant and skips it, but the other app's trigger in your Zap may not.
Connect NorthStar to Zapier in 3 steps
- 01
Open your apps
In Zapier, go to the Apps page of your account and click + Add connection. You need a NorthStar account first, with write access to the workspace where cards should appear.
- 02
Pick NorthStar
Search for NorthStar by GrowthHackers in the dialog, select it, then click Add connection. A new tab opens on the NorthStar side to start the link between both accounts.
- 03
Sign in and allow access
Sign in to NorthStar in that tab and grant Zapier access to the account. The connection is saved once; every Zap step that uses NorthStar picks it from a list afterwards.
Your first Zap: log and announce every new NorthStar card
GoalEach time a card is created in NorthStar, add it to the backlog sheet leadership reads, then post it to the growth team channel.
- 01
Create the Zap and pick New Card
Start a new Zap, choose NorthStar by GrowthHackers as the app and
New Cardas the event, then select the NorthStar connection you added earlier. - 02
Test the trigger
Run the test: Zapier brings back the three most recent cards of the account, so you map fields from a real one. If the workspace is empty, add a test card first.
- 03
Add the spreadsheet row
Click the plus icon, add the spreadsheet app and its new row action, pick the backlog sheet and map the card fields into its columns. Test it and read what came back.
- 04
Add the channel message
Add a second action for the team chat and map the card's idea into the message. This second action makes it a multi-step Zap, which needs a paid plan.
- 05
Publish
Click Publish to switch the Zap on. On the free plan, keep one action only: the sheet or the message, not both. New cards then flow on their own.
The NorthStar trigger
1 event starts a Zap when something happens in NorthStar by GrowthHackers, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Card
Instant triggerIn Zapier“Triggers when a new card is created.”
Starts your Zap whenever someone adds a card in NorthStar, whether it came from a teammate typing it in or from another Zap. It is the single event NorthStar reports to Zapier, so it is the door for anything that should follow a new idea.
The NorthStar action
NorthStar by GrowthHackers gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Card
ActionIn Zapier“Creates a new card.”
Adds a new card to NorthStar from whatever the trigger brought in, so ideas from customers, sales or support reach the growth backlog without retyping.
When a NorthStar Zap breaks
Zapier links no help article to NorthStar and documents no app-specific limit. The failures below come from how Zapier works in general, applied to this app.
Four cases cover most of what goes wrong. If a Zap still misbehaves after these checks, the Zapier troubleshooting guide walks through the diagnosis step by step.
A loop between New Card and Create Card
A Zap that creates cards in the workspace its own New Card trigger watches sets itself off again and again, and burns the task count fast.Old ideas never arrive
A Zap only reacts to what happens after it is switched on. Cards that already exist are not picked up; moving the backlog is a separate job.Idea too long
Create Card wants a summary of 50 characters at most. Mapping a long form answer into Idea is the usual reason the step will not go through.Flood after an import
Adding a large batch of cards at once can trigger Zapier's flood protection, which holds the runs back instead of firing them all.
Need help automating NorthStar by GrowthHackers with Zapier?
A person reads every message.



