Automove jobs: Overview

The job automove feature simplifies your workflow by making jobs move from stage to stage in a pipeline or from custom job status to Active on their own. Use the feature with automations, linked elements or both. Create dependency to let jobs automatically jump ahead every time all actions within a stage or action in job status are completed by a team member or client.

Tip

Download the automove triggers checklist to know when automove works and when it doesn’t.

Job automove, explained

Automove may mean two different things:

• Job automove from stage to stage. Moves cards through the pipeline when set conditions are met.

• Automove for custom job statuses . Custom status is automatically changed to Active once the conditions are fulfilled.

Below, we describe job automove from stage to stage. If you want to learn more about custom job status automove, proceed to the section .

1. While adding stages and automations to a pipeline , toggle on Automove jobs in the stages where you will want jobs to automatically move ahead.

   

2. Once you add a job to a pipeline, automations in the first stage are triggered.

3. If Automove jobs is toggled on for the first stage, the job automatically moves to the second stage once all the actions in the first stage are completed (e.g., a proposal signed, an invoice paid, etc.), then the automations for the second stage are triggered—and so on. Manually linked entities also impact automove.

If several automations are added to a stage that has Automove jobs toggled on, the job automatically moves once all actions are completed.

You can see all the pending action items on the job card. See more ways to manage pending action items here .

4. Once a job arrives in its final stage and all actions are completed, you can archive it. You can’t toggle on Automove jobs for the last stage of a pipeline.

How automove works with automations

The job automove feature works only with automations that require specific user actions, either from a team member or from the client. Check out the details below and click on the name of each automation to find out how to employ it:

How automove works with manually linked elements

Sometimes you may prefer to manually add an existing invoice, proposal or another element to a job, rather than use automations to create it. Besides, some elements (e.g., documents) can only be linked manually. However, elements linked manually trigger the automove just the same. Check out the details below and click on the name of each element to see how to employ it:

How automove works for custom job statuses

Unlike automove jobs between stages, Automove from custom to Active job status occurs within a single stage:

1. Once the job status is changed to a custom one, the job remains in the same stage, and automove triggers for a stage don’t affect it.

2. When the configured conditions inside the custom status are met, the job automoves to the Active status. After this, it moves through the pipeline by following the general rules.

For example, a custom Missing info status has been assigned to the job, with automation configured to retrieve the information via client request . Until clients provide information, the job card will be displayed with Missing info status. When clients provide answers via client requests, the status will automatically change to Active.

Keep in mind:

• If several automations are added to a custom job status, the job status will be changed to the Active one automatically once all actions are completed.

• The automove jobs for custom job statuses feature recognizes invoices, proposals, organizers, client requests, tasks, documents, and chats with client tasks, even if they are manually linked to a job custom status within an automation set. If there are linked elements with incomplete actions, the job won’t change the status to Active.

Job automove examples

Share

Link copied