> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflow-triggers/workflow-trigger-contact-created.md).

# Workflow Trigger: Contact Created

The *Contact Created* Workflow Trigger will add a contact to this workflow whenever one is created. This can be a very helpful trigger for many applications such as customer onboarding processes and lead nurturing. This article will outline how to set up a workflow using the *Contact Created* Workflow Trigger.

**Step 1:** Start a new workflow or edit an existing one

**Step 2:** Creating and Editing the Trigger

* Click “Add New Workflow Trigger”

{% embed url="<https://lh6.googleusercontent.com/y2sV0amGOb6UwbhFMG_nqsxHAeCMAFMEiGEVAE5Orxv3Zfaf4oyGowYE9pQbdedyKQZHXs9e1bjHK411nAFIkefqRpfVPKLLxXqVVRAR-Ya8M9PosIK-MUE_WccQqGVP-I7gZY3dqGJt-AInqc7IbJA>" %}

* Select **Contact Created** in the **Contact** section of the Workflow Triggers Menu or use the search feature. This will open the Contact Created Trigger setup menu.
* (Optional) Change the Workflow Trigger display name under **Workflow Trigger Name**.

*Note: that this will only impact the trigger’s display name within the workflow builder*

* In its base form, any newly created contact will be added to this workflow, but you can filter this to only include specific contacts
  * **Has Tag** will only add contacts to this workflow that have a particular tag assigned to them
* **Custom Fields** are also available to only include contacts that meet custom parameters that you have set up elsewhere.

*Note: Custom fields would commonly be added to a form*

* Press **Save Trigger** in the bottom right corner of the Trigger setup menu

{% embed url="<https://lh5.googleusercontent.com/1L8jRnFqsm2e8KRUrkPvRIMDx-iWIOlh0Wgg6Tfe6ovAIcFdUdg2H72xQI4VQvC1XUrwfdIHxVG7RdKEL0IcBSjRrwM7v25XxVMazgdB4CVNQgtIR3ZsnaChxu1OEjGGh42IpXAyLuprVtVrk5CH-tg>" %}

**Step 3:** Set up applicable Workflow Action(s). We have multiple articles available to explain the setup of each of the Workflow Actions. Feel free to review our articles on these for more information on setting these up.

***Pro Tip:*** You can use any Workflow Actions to be set into action by the trigger or you can leave this workflow without any actions.

**Step 4:** Press **Save** in the top right corner of your browser to save the workflow

* If your Workflow is ready to be enabled, make sure the toggle switch under **Save** is set to **Publish**
* Be sure to test your Workflow to make sure it is set up correctly using the **Test Workflow** button next to the **Publish** toggle switch.
  * For an in-depth overview of Workflow Testing see our article, “Using the Testing Features in Workflows”

{% embed url="<https://lh5.googleusercontent.com/o811glhHurL4dpcZ6hdiA1SDq9db8HD7wzm8bvKh555Azx8Nb1yM96UYwUFUUWr2LCtpcxhuFwxmTGo7vUWG4NyIAXljBQFkOaRljc4izmYhsAxyXF9a7lkeGhgE1K-wfAvmvbkDhD4WDZZqseIT_Gw>" %}

Now your workflow is set up and ready to go with the *Contact Created* Workflow Trigger.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://software-help-docs.gitbook.io/knowledge-base/software-guide/workflow-triggers/workflow-trigger-contact-created.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.