> 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-actions/workflow-action-add-to-workflow.md). # Workflow Action: Add To Workflow Adding a specific contact to separate workflows for sorting or continuing a process can be automated. Let’s say that your lead submitted a form with a custom field and you want that information to determine if they go to an autoresponder. Another contact completes a product and you want to send them to a workflow to offer them a supplementary course automatically. Or a contact books an appointment and you want to send a confirmation then transfer them to a flow to follow up until the event and pass the input parameters to this new flow. You can accomplish this with the Add To Workflow action we will go over this and how to use it. {% embed url="" %} **Step 1:** Start a new workflow **Step 2:** Setting up the Workflow Triggers * Under Workflow Triggers, select “Form Submitted” in the “Contact Actions” section of the Workflow Triggers Menu * Filter for the form that you can create from Sites > Forms > Builder * Filter for the Custom field you can create from Settings > Custom Fields {% embed url="" %} * Click “Save Trigger” in the bottom right of your screen. {% embed url="" %} * Under Workflow Triggers, select “Product Completed” in the “Membership” section of the Workflow Triggers Menu * Add a filter for the specific membership product involved * Click “Save Trigger” in the bottom right of your screen. {% embed url="" %} * Under Workflow Triggers, select “Appointment Status” in the “Appointments” section of the Workflow Triggers Menu * Select the Event Type * Filter for the Calendar and the appointment status * Click “Save Trigger” in the bottom right of your screen. {% embed url="" %} **Step 3:** Adding the *If/Else* Action and *Add To Workflows* Action * Click on the “+” symbol below the trigger to add an action. * Under Actions, select “If/Else” in the “Conditions and workflow” section of the Actions Menu or use the search feature * Add branches and choose the segment parameters to filter for the individual workflow triggers and how the contact entered the flow. (see the article on if/else for more information) * Save the action {% embed url="" %} **Add to Workflows** * Click on the “+” symbol below each specific branch to add an action. * Select the workflow from the dropdown * Pass Input Trigger parameters for flow that are dependent on triggers for functionality (see screenshots below) * Save the actions {% embed url="" %} {% embed url="" %} **Please Note:** Passing input parameters will allow you to use values and wait steps of the event/appointment type in the new workflow to properly track an appointment and when communication happens. See our articles on appointment reminders for more information. (See screenshot below) {% embed url="" %} {% embed url="" %} **Step 4:** Customize to your preference * Add actions and customization to your preference * Publish and save the workflow (top right of the screen) {% embed url="" %} --- # 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-actions/workflow-action-add-to-workflow.md?ask=&goal= ``` `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.