> ## Documentation Index
> Fetch the complete documentation index at: https://services.docs.growcrm.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Automate Project Creation After a GrowCRM Service Purchase

> Automatically create projects, assign team members, and notify clients whenever a service checkout or subscription renewal completes.

The **Checkout Automation Settings** tab on a service lets GrowCRM do the operational work for you the moment a payment goes through. Instead of manually creating a project every time a customer buys, you configure the rules once and GrowCRM generates the project automatically — with the right status, due date, and team members — without any further action from you. This tab is available on every service and supports two independent triggers so you can handle first-time purchases and recurring subscription renewals differently.

## The two automation triggers

GrowCRM fires checkout automation on two distinct events. Each trigger has its own set of settings, configured independently.

<CardGroup cols={2}>
  <Card title="New Checkout Completed" icon="cart-check">
    Fires when a customer completes their **first or one-time purchase** of a service. Use this to kick off onboarding projects or initial deliverable workflows.
  </Card>

  <Card title="Recurring Payment Completed" icon="rotate">
    Fires on **every subscription renewal** after the first payment. Use this to create a fresh project for each billing period, keeping ongoing work organised by cycle.
  </Card>
</CardGroup>

## Configuring a trigger

For each trigger, toggle **Create a new project** to enable automation. Once enabled, the following configuration fields appear.

<ParamField body="Project Status" type="string">
  The status assigned to the newly created project. Choose from **Not Started**, **In Progress**, **On Hold**, **Cancelled**, or **Completed**. Most teams use "Not Started" so the project enters the normal workflow queue.
</ParamField>

<ParamField body="Project Duration (days)" type="number">
  The number of days added to the purchase date to calculate the project's due date. For example, entering `14` sets the due date to two weeks after the payment is processed.
</ParamField>

<ParamField body="Assigned Users" type="array">
  One or more team members to assign to the new project automatically. Every assigned user receives an email notification when the project is created.
</ParamField>

<ParamField body="Notify client (email)" type="boolean">
  *Available on the **Recurring Payment Completed** trigger only.* When enabled, the client receives an email each time a renewal creates a new project. Useful for retainer services where clients expect a confirmation that work for the new cycle has started.
</ParamField>

## How custom order form answers are included

If you have attached a [custom order form](/checkout/custom-forms) to the service, the answers the customer submits at checkout are automatically appended to the newly created project's description. This means your team has the customer's requirements, preferences, or specifications right inside the project — no need to chase down a separate form submission or copy-paste information manually.

<Note>
  Custom order form answers are appended to the project description as plain text. They appear for projects created by **both** triggers — initial checkout and recurring renewals — provided the customer submitted the form at the time of purchase.
</Note>

## Practical examples

<Accordion title="Auto-assign a team member and set a start status">
  A web design agency sells a "Website Redesign" service. Under **When a new checkout has completed**, they enable **Create a new project**, set **Project Status** to "Not Started", assign their lead designer in **Assigned Users**, and leave **Project Duration** at `30` days. Every time a client purchases the service, a project is created immediately, assigned to the designer (who gets an email alert), and given a 30-day deadline — all without any manual step.
</Accordion>

<Accordion title="Create a fresh project on every subscription renewal">
  A content agency sells a "Monthly Blog Package" subscription. Under **When a recurring payment has completed**, they enable **Create a new project**, set **Project Status** to "In Progress", enter `28` in **Project Duration**, and assign their content team. They also enable **Notify client (email)** so each subscriber gets a confirmation email when their new monthly project is opened. The client always knows work has started for their current billing cycle.
</Accordion>

<Accordion title="Capture custom requirements inside the project">
  A branding studio attaches a [custom order form](/checkout/custom-forms) to their "Logo Design" service that asks for brand colours, industry, and inspiration keywords. When a customer checks out and submits the form, GrowCRM creates a new project and appends the customer's answers to the project description. The designer opens the project and immediately has every brief detail in one place.
</Accordion>

<Tip>
  Use **Project Duration** to reflect your realistic delivery window, not an aspirational one. The due date flows into GrowCRM's project timelines and client-facing communications, so an accurate estimate builds trust from the moment of purchase.
</Tip>

## Related pages

* [Custom Order Forms](/checkout/custom-forms) — Build forms that collect customer information at checkout and feed into automated projects.
* [Orders Overview](/orders/overview) — See how completed checkouts become orders and track their status.
* [Subscription Management](/orders/subscriptions) — Manage active subscriptions and review recurring payment history.