VesselCreate a repeatable workflow and review its runs.
Begin with one repeatable task
On the Actions page, Create action opens the starting choices. Pick the workflow that best matches your task, then give it a recognizable name so your team can distinguish it from other Actions.
Open Actions and choose a starting workflow. In the builder, follow Your action and select each step to configure it. Choose a source such as Latest completed sermon, a specific sermon or series, or a connected YouTube / RSS source where offered.
Choose when it should run: Only when I run it, On a schedule, When a new recording arrives, or Follow a content calendar, according to the available setup. Fill in the required fields and review the destination and any writing persona before saving.
Run and inspect
For a first test, choose Only when I run it, save the configuration, and run it with a recording you recognize. Open the resulting run to check the source, the step that ran and the output. If a step needs attention, read its message before changing the workflow.
Start with a manual run when possible. Open Recent runs and inspect the result and any errors. For a newsletter review step, check the content and recipients before any delivery action. A configured workflow is not proof that a run succeeded: verify the run status and resulting output.
Example: prepare a recurring review
Harbor’s sample team wants a newsletter draft after a recording arrives. They start with a workflow that prepares a newsletter for review, select a connected source and inspect each step under Your action. They choose a writing persona suited to group leaders and verify that the draft is intended for review. The builder describes an account-email review option as using the account email and says no audience is contacted by that step.
Start with Only when I run it when practical. Run the workflow against a known completed sermon, then open Recent runs. Confirm the source, read the resulting draft and inspect any error shown on the run. Once the team understands the output, they can choose an appropriate scheduled, new-recording or calendar trigger and check the next run.
Troubleshoot a run
If a source is missing, check the selected sermon, series or connection and whether the recording is ready. If the trigger does not fire, check the saved trigger and its required connection or calendar. If the run completes but the content is unsuitable, refine the persona or instructions and test again; a successful run only means the workflow completed, not that its output has editorial approval.
Do not treat a draft as a sent campaign. Review the final content and delivery setup separately. See connections and calendars and Outreach review.
Pick a trigger deliberately
A manual trigger is useful while the team is learning the flow. A scheduled trigger runs on its configured timing; a new-recording trigger depends on the selected connection; a calendar trigger depends on the selected calendar. Choose the one that corresponds to the event you actually want, and inspect the relevant step in the builder before saving.
When a run is complete, follow the output to its own workspace. A newsletter draft needs its own editorial and delivery review. If the run failed, the details can narrow down whether the source, trigger or a later step needs attention.
Was this a useful next step?
Take the idea into the workspace.
Keep this guide nearby. Start small, review the result, and make it your own.
Try it in Vessel