| Subject | Introducing Noco Factory: hand off a task, get a pull request |
| Preheader | An AI coding agent for your GitHub repos. Beta on paid NocoDB Cloud plans. |
| Audience | Users in paid NocoDB Cloud workspaces (Plus and above) with a developer signal: an API token in use, an MCP connection, a script, an OAuth client, a GitHub integration, an external PostgreSQL or MySQL source, or a webhook to a custom endpoint. Add everyone who clicked the Noco Factory link in the P.S. of the Classic Apps email. |
| Exclude | Free and self-hosted workspaces (Noco Factory is Cloud only), workspaces that already use it, and users whose only signals are Zapier, Make or n8n tokens and webhooks. |
| Send | About a week after the Classic Apps email. |
| Goal | A connected GitHub repository and a first session. |
Merge fields: Brevo contact attributes only. The greeting uses contact.DISPLAY_NAME, and falls back to the part of contact.EMAIL before the @.
The email shows the Connect your code step that people see when they open Dev Factory. The whole panel and the Connect GitHub button both go to https://app.nocodb.com/?kind=factory, with utm_source=email&utm_medium=campaign&utm_campaign=noco_factory_launch. utm_content is panel or build_cta, so you can see which one people clicked.
The logos are PNGs (Gmail drops SVG), served from https://cdn.nocodb.com/emails/v2/introducing-factory/. The source copies are in public/comms/campaigns/introducing-factory/. The CDN caches them for a year, so to change one, upload it under a new name, or invalidate the CloudFront cache after you upload.
Book a call goes to https://cal.com/nocodb/30?utm_source=email&utm_medium=campaign&utm_campaign=noco_factory_launch&utm_content=book_call.