Skip to content

Actions

Connect a source or content calendar

Give an Action a source and schedule you can maintain.

What you’ll work toward

Give an Action a source and schedule you can maintain.

Connect a source

Choose Manage connections on the Actions page. Add the YouTube channel or RSS feed using the options offered, then check the connection and select it in your Action. A connection watches for material; it does not by itself create or send content.

In Actions, open the source management area. Follow the connection flow for the offered YouTube or RSS source and confirm the correct feed or channel. Return to the Action builder and select it under the source step. A connected source is useful only if it has an eligible recording for the workflow.

Use a calendar deliberately

Open Content calendars and choose Create calendar to build a plan. Review each day’s focus, date and time zone, then link the intended calendar in the Action builder. Choose Follow a content calendar only when you are ready for the configured Action to follow that plan.

Choose a content calendar when the action should follow its plan, and inspect dates and settings before enabling the workflow. Use a manual run to check the output first. Then inspect Recent runs after the next trigger to confirm the correct source was used.

If no run appears, check that the Action is enabled, its source is connected, and its trigger and calendar are configured. The displayed run details are the best place to investigate an individual failure.

Example: connect, test, then schedule

A sample Harbor team has a YouTube channel for its services. In Actions, they use Manage sources and follow the connection flow for the channel or feed. Back in the builder, they select Connected YouTube / RSS and choose that source. They run a known completed sermon first so they can compare the generated draft with the recording.

A content calendar can coordinate work with dates, but check its entries and time settings before using Follow a content calendar. A calendar entry, a trigger and a completed run are different states. After a trigger is due, open the run details and verify the selected source and result.

If a connection is unavailable, review the connection’s access and the feed or channel selected. If the calendar option has no selection, choose a calendar in the builder. Correct the setup and test again before relying on the automation. See Build your first Action for the full sequence.

Keep the source predictable

A connected feed may contain more than Sunday sermons. Check that the intended recording is eligible and that the Action’s source choice matches the work your team wants to prepare. A test against a known source makes it easier to spot an unexpected selection.

If a run needs intervention, open its details and note the trigger, selected source and displayed error before changing several settings at once. Correct one issue, run again and review the new result. See Build your first Action.

Was this a useful next step?

Your 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