> For the complete documentation index, see [llms.txt](https://docs.corpdev.ai/corpdev.ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.corpdev.ai/corpdev.ai-docs/run-recurring-and-event-based-work.md).

# Run recurring and event based work

An automation pairs a trigger with an action. It can create or update a document, refresh supported columns, scan for signals or deliver a brief. Available triggers and actions depend on the workspace and plan.

## Create a rule

1. Open **Automation** and select **New automation**.
2. Give it a name that states the purpose and scope.
3. Configure **When this fires**. For recurring work, choose the frequency and timezone; for an event, choose the relevant pipeline, stage, folder or other scope.
4. Configure **What this does**, including the prompt, target document or template.
5. Check the destination folder and delivery recipients.
6. Review the validation and next-run information before saving. Leave the rule disabled while preparing it if you do not want it to fire yet.

For a first recurring report, use a small scope and an internal recipient. Inspect the first completed result before widening the scope or adding external delivery.

## Choose a trigger

| Trigger                                | What to check                                                      |
| -------------------------------------- | ------------------------------------------------------------------ |
| Recurring schedule or run once         | Date, time, frequency and named timezone.                          |
| Pipeline stage enter or exit           | Selected pipeline, source/destination stage and re-entry behavior. |
| Stage dwell                            | Stage, duration and whether it repeats.                            |
| Manual stage action                    | Which opportunities the action is intended to run on.              |
| New Source Files uploads               | Folder or whole-room scope and the quiet period after uploads.     |
| Document or agent events, when offered | Exact event, target scope and debounce behavior.                   |

A quiet period waits for activity to stop before firing. Continued uploads or edits can postpone the run. Do not assume the first event starts an immediate job.

## Write the action

For a new document, choose the template or write a complete brief, then confirm where the output will be saved. For an existing document, specify how to revise it and preserve useful history. Use the provided field chips and preview for deal- or row-specific values.

Example: “Prepare a weekly pipeline update. For each active opportunity, summarize the current stage, material activity and next action. Separate missing information from confirmed updates.”

## Control delivery

Inspect **Email it to**, workspace-wide recipients, external-recipient settings and whether the email includes a link or document content. Workspace-wide membership can change after the rule is saved. External delivery creates an ongoing disclosure path for future outputs.

Where shown, **Standing externals** lists approved external recipients and provides revocation controls. Revoking a share does not retrieve an already delivered attachment or email body.

## Verify, pause and recover

Use the rule's run history to check the action result and per-recipient delivery outcomes. A successful generation does not necessarily mean every email arrived. Check failures before using a resend control.

Use the **Enabled** switch to pause future runs while retaining configuration. **Run now** starts work immediately and may consume credits or send configured messages. Deleting a rule can also remove its run history; read the confirmation before deletion.

If a rule fails, inspect its target, permissions, credits and provider connection. Correct the cause before retrying.

## Workflows, when enabled

Open the **Workflows** area under Automation and choose **New workflow**. Use the builder to define the steps and connections, including required input parameters. Save the definition and publish a runnable version before starting a run. Publishing the workflow makes that version available to run; it does not itself prove that a run succeeded.

Start a run with the required inputs, check the selected version and follow **Recent runs**. Open a run to inspect its status and individual step outcomes. Pending, running, paused, completed, failed and terminated states have different meanings. Review any steps that send messages or change workspace data before starting a workflow.

## Macros, when enabled

Macros group related automation rules. Manage the available macro groups in Automation, inspect their rules and destinations, and use the group switch to control whether they are enabled. A managed macro can provide a configuration or customization flow rather than unrestricted editing of every rule. Review prompts, recipients and scope after customization, then inspect the first result.

Pausing a group should not be assumed to undo actions already completed by its rules.