Your Greta frontend.
Your Netlify team.

Before you start

• A Greta account with an owned Agentic project and access to deployment.
• Access to the private Greta extension and permission to install and deploy on your Netlify team.
• A saved, synced frontend that can produce a static build. Server-rendered Next.js and legacy projects are not supported by this export.
• If your frontend calls a backend, deploy that backend in Greta first. This integration does not migrate backends or databases to Netlify.

1. Install and authorize Netlify deployments

1. Open the Greta extension in Netlify while signed in to the team that should own the site. During the private pilot, request access if it is unavailable.
2. Install Greta on that team and open its configuration page.
3. Select Authorize Netlify deployments. Review Netlify's consent screen before approving, then return to the extension.
4. Wait for Netlify deployment authorization saved before connecting Greta.

The saved authorization allows deployment jobs to continue after you close the configuration page.

2. Connect your Greta account

1. In the production Greta app, open Settings → Connectors and create a Netlify-specific API key.
2. Paste that key into Greta Netlify API key in the extension, then select Connect Greta.
3. Confirm Greta account connected. The project selector lists that account's eligible projects.

Keys expire after 90 days and can be revoked in Greta. Use a production key for the production integration—not a staging key, password or browser session token.

Authorized members of this Netlify team can deploy projects from the connected Greta account. Connect an account whose projects you intend to make available to that team.

3. Select and deploy a project

1. Choose your project. Use Next and Previous to browse additional projects.
2. Leave automatic redeploy unchecked if you want manual updates only.
3. Select Deploy to Netlify. Greta prepares the frontend ZIP and deploys it to a site in your installing Netlify team.
4. Wait until the deployment reports Live, then select Open deployed website.

Check the homepage, an internal route, and any forms or API calls your app uses. A Live static deployment does not by itself prove that the app's backend or authentication is configured correctly.

Later manual deployments use Redeploy to Netlify and reuse the linked site rather than creating a new one.

4. Redeploy when you publish

Automatic redeploy is opt-in. Before the first deployment, enable Redeploy when I publish this project in Greta. For an already linked project, use Automatic redeploy on Greta publish.

Make a change in Greta and publish it. Greta queues a signed publish event and deploys that published build revision to the same linked Netlify site. Editing without publishing is not the publish trigger.

Check the deployment status and Netlify deploy log, then confirm the change is visible at the existing site URL. Turning automatic redeploy off stops future publish-triggered updates; it does not take the existing site offline.

Credentials and disconnecting

• Saved Greta and Netlify credentials are encrypted server-side. Do not put them in frontend source or public VITE_* environment variables.
• Use Disconnect Greta to remove the Greta connection and disable its automatic redeploys. Revoke the Greta key in Settings → Connectors if it is no longer needed.
• Disconnecting or uninstalling does not delete your Netlify sites.
• The Netlify OAuth authorization is a separate grant. Revoke it in your Netlify account's application settings when you no longer want Greta to have that access.

Troubleshooting

Still stuck? Contact Greta support with the project ID, Netlify site/deploy ID, approximate time and the visible error. Do not send API keys or access tokens.