Connect Netlify

Connect

Netlify builds and hosts sites. Connecting it lets MaShop create the sites of your project on your own account and launch their builds.

What MaShop can do with Netlify

• Creates two sites from the same repository: one for your public site, one for your back office. The second carries the same name with an admin suffix.
• Pushes the environment variables each site needs, before the build, so the public ones are baked in.
• Triggers the build. It writes the live state only once Netlify reports the build ready and the address itself answers.
• Attaches a custom domain when you ask the assistant for one, and hands back the DNS records to enter at your registrar. Propagation is announced between 5 and 60 minutes.

The catalogue declares three tools: build.logs, deploy.trigger and domain.dns. Netlify is the only official connector with three rather than four. None of them has an executor yet.

What it touches

• Two sites on your Netlify account, and their build logs.
• Their environment variables. MaShop sets the database ones: the Supabase address, the public key, the service key and the default language. It adds the public site address on the storefront, and a project identifier on the back office.
• The DNS of a domain you explicitly ask to attach.

Payment and email keys are never pushed. Those are yours to add.

Default permissions

Tool	Level	Default state
build.logs	Read only	Allow
deploy.trigger	Write and edit	Ask
domain.dns	Critical action	Ask

Before your first project

The setup wizard asks for Netlify at step three, before any project exists. Unlike GitHub and Supabase, this step never blocks the wizard, and you can come back to it later.

The token is stored on your account. One authorization covers every project you own.

Connect it

1. Open your project in the workspace.
2. Click the gear in the top bar, Project settings.
3. Open the Deployment tab.
4. On the Netlify card, click Connect. A popup opens Netlify.
5. Approve, and let the popup close on its own.

Check that it works

• The Netlify card reads Ready to deploy.
• The Publish button changes to Update once the project has been published once.
• The address of your site appears in the top bar. It is a site on your account, not a MaShop site.
• While the account is missing, publishing refuses with: Netlify is not connected. Connect it to publish.

Limits

• Two sites per project, counted as one deployment against your quota.
• The very first build of a publish does not consume the quota.
• The public site is required. If the back office site cannot be created, the public deploy carries on rather than failing both.
• Renaming the project identifier renames the subdomain only when that name is free. Otherwise the identifier is saved and the address does not move.
• Deploying is free and open to editors. The very first publish requires a paid plan.
• An archived or deleted project can no longer be deployed.

When it breaks

• Publishing refuses on the connection. The account is not connected. Reconnect from the Deployment tab.
• The token is invalid or expired. The deploy of the public site stops and asks you to reconnect Netlify, rather than reporting a success that never happened.
• Netlify says ready but the address does not answer. The state stays not live. That is deliberate: a green badge over a dead address is worse than a red one.
• The custom domain does not resolve. The DNS records are not in place at your registrar yet, or propagation is not finished.

Remove the connection

Project settings, Deployment tab, Netlify card, Disconnect. A confirmation asks Disconnect this service, and tells you that you can reconnect at any time.

MaShop deletes the token it stored. Your sites, their builds and their domains stay on your account and keep serving. The authorization stays listed in your Netlify settings until you revoke it there. Publishing and updating stop until you reconnect.

See also

• Connect GitHub
• Connect Supabase
• Netlify documentation