Connect your product

Tell YouGrow about your app and the steps of getting started in it, then hand the coding to your developer.

About 15 minutes, plus your developer's time · Admins · Once per product

Try a sandbox first

A sandbox is a pretend product with a demo catalog and one test user: you. Try a journey on it before anyone writes code. It doesn't count as your product, on Home or for invites.

1. Open Products and press Create sandbox.
2. Press Create, then Open the sandbox.
3. On the Sandbox tab, your test user has your sign-in email. To change it, edit it and press Save test users. It must be yours or on your verified domain.
4. Build a journey on the sandbox and publish it.
5. Back on the Sandbox tab, press Signed up, then a step, to act as your product.

Connect a product

1. On Products, press Connect a product.
2. Type a Name, such as your app's name.
3. Under Which copy of your product is this?, choose Staging, Production or Not sure yet. Have both? Connect staging first, to test safely.
4. Press Create.
5. Copy the key id and the secret into your password manager, to share with your developer. The secret is shown only once.
6. Tick I've stored the secret somewhere safe, press Next, then Learn from my repo.

Learn your steps from your repo

YouGrow reads your code and suggests your onboarding steps, events and facts. It never changes your code.

1. On the product's Learn from repo tab, press Connect GitHub and choose the repositories it may read. On GitLab, or a public repo? Press Add a repository by address (GitLab or public) instead.
2. Tick up to 3, such as your web app and your backend, and press Learn from repo. It takes a few minutes, and you can leave the page.
3. Read what it found. The trusted items are already ticked. Untick anything that's wrong.
4. Under Add to the catalog, type Your app's web address, such as https://app.yourproduct.com. This turns each step into a link in your emails.
5. Press Add selected to the catalog. The Catalog tab opens with what you kept.

No steps found? Run it again on the repository that holds your sign-up and setup, or add the steps yourself on the Catalog tab. In a company's GitHub organisation, an owner may need to approve the app first. See how connecting works.

What to send your developer

1. The key id and secret, through your password manager.
2. The prompt from Copy prompt on the Integration guide tab. A coding agent such as Claude Code or Cursor can work from it. It has no secrets in it.
3. The developer docs.

Sign-ups come first: without them, no journey sends anything. Each sign-up should include consent, or only the welcome email goes out. Steps come next. The guide lists every task in that order, and says what happens if it's skipped. Details: sending users. The Setup tab ticks each part off as it arrives.

Test the context endpoint (optional)

Only for emails that tell people what their own results mean. Your developer builds the context endpoint and adds its address on the Settings tab, with Enabled ticked.

1. On the Test connection tab, type one user's id, as your app knows them.
2. Press Test connection. A good answer starts "Valid context in" and lists their steps, facts and insight sentences.

Check it worked

• The Setup tab ticks Learn your product from its repo and Receive your users' sign-ups and steps.
• The Events tab lists what your app sends. Refused writes show under Recent rejections, with the reason.
• On Home, Launch product says "Receiving events".

If you see this

Next: Invite your waitlist