Workflows & Automation

The three main automation tools

Most users will spend their time in three related areas:

• Workflows for multi-step automated logic
• Daily Check-ins for scheduled outreach, reminders, and recurring tasks
• Schedule Builder for simpler task scheduling and follow-up presets

Around those tools, you also have Connectors that link NetShow to outside systems and Social publishing paths that move created content into live channels.

If you remember nothing else from this guide, remember this:

• use a workflow when the task has several steps
• use a schedule when the task mainly needs timing
• use a check-in when the task is about consistent proactive contact

Start with a simple question: what should happen automatically?

Before creating any automation, write one clear sentence:

“When this happens, my agent should do this.”

Examples:

• “Every weekday at 8:00 AM, my agent should send me a lead summary.”
• “If a client has not replied in three days, my agent should remind me to follow up.”
• “Every Monday, my agent should check in with active clients by text.”
• “After I generate content, I want it ready for social scheduling.”

That sentence tells you which surface to use and how complicated the setup needs to be.

Workflows: building multi-step automation

Workflows are the right choice when you need more than one action or decision. In the backend, a workflow stores a name, nodes, connections, and variables. In practical terms, that means a workflow is made of building blocks connected in sequence.

Use workflows when your task looks like a chain instead of a single reminder.

Good workflow examples:

• capture a lead, enrich the details, and notify your team
• schedule a recurring report, generate it, and deliver it
• trigger an internal follow-up when a condition is met
• coordinate content, alerts, and channel handoff

What you will see in the workflow builder

The workflow builder usually centers around:

• a workflow name
• nodes
• connections between nodes
• variables or data the workflow uses

A good name matters more than people think. “Workflow 7” is hard to maintain. “Monday Sales Summary” or “3-Day No-Reply Follow-Up” is much easier to understand later.

What a node means

A node is one step in your automation. One node might represent a schedule. Another might represent a message, a report, or a check. When you connect nodes, you are telling the system what should happen next.

If you are new to automation, build the smallest working version first. A simple two- or three-step workflow is easier to debug than a complicated one with too many branches.

Saving and updating workflows

When you save a workflow, NetShow stores the structure so it can be reused and updated. If a workflow contains a schedule node, the platform can also create or update a related scheduled task record behind the scenes. That means your workflow can live both as a design and as an active schedule.

This is helpful because you do not have to manually recreate timing logic every time you edit the workflow.

Daily Check-ins: proactive outreach and recurring tasks

Daily Check-ins are for scheduled outreach that feels personal, operational, or relationship-based. These are especially good when you want your agent to do recurring work without waiting for someone to start the conversation.

This can be personal or business-focused. A check-in could remind you to complete a routine, nudge a client, trigger a call, send an email, or ask for an update.

What you configure in a Daily Check-in

The daily check-in flow is more detailed than a simple reminder because it is meant to support real communication. In the current controller, the form validates fields such as:

• category
• task name
• task instructions
• timezone
• frequency
• preferred communication method
• email or phone number
• agent selection
• optional call forwarding

Depending on the frequency you choose, you may also set:

• one-time month, date, and time
• daily time
• weekly day and time
• monthly date and time
• interval-based cadence
• annual month, date, and time

That means the system supports more than a basic daily reminder. It can handle one-time events, recurring patterns, and longer-cycle follow-ups.

Communication method choices

One of the most important choices in Daily Check-ins is how the task should reach someone. The current flow supports communication preferences such as:

• SMS
• call
• email

This is powerful because it lets you match the delivery channel to the task. A personal reminder may be better as a text. A formal update might be better by email. A voice-first workflow may be best as a call.

When to use Daily Check-ins instead of workflows

Choose Daily Check-ins when the main job is timing plus communication. If the task is basically “reach out on a cadence,” Daily Check-ins are often the simpler and better fit.

Examples:

• send me a morning accountability prompt
• call back new leads every weekday at noon
• send patients a check-in message each evening
• remind customers about an upcoming appointment

If the task needs a complex series of conditional steps, move to workflows instead.

Schedule Builder: the easiest way to start automating

Schedule Builder is one of the friendliest automation surfaces in the product. It is a great entry point for users who want automation but do not want to start with a full visual workflow system.

The page is built around the idea of quick presets plus custom scheduled tasks. It also surfaces existing schedules so you can see what is active, what is paused, and what will run next.

Preset schedules

The current preset flow includes options like:

• Follow up tomorrow
• Weekly check-in
• Daily lead check
• Remind if no reply in 3 days

These presets are useful because they turn common automation patterns into one-click starting points. If one of them matches your need, use it. There is no prize for making a custom schedule when a preset already does the job cleanly.

Custom schedules

If the preset is close but not quite right, create a custom schedule. In the current schedule builder flow, you typically provide:

• the agent
• a task description
• a frequency such as once, daily, or weekly
• a scheduled time

That is enough to create a practical follow-up task without building a full workflow from scratch.

What the schedule list tells you

The page also surfaces existing schedules with details like:

• name
• description
• task type
• status
• next run time
• associated agent

That list matters because automation only feels trustworthy when you can see what is coming next. If something is active, paused, or pending, you should know that without digging through logs.

Choosing the right frequency

Scheduling mistakes usually come from choosing the wrong rhythm, not from filling the form out badly. Before you set a cadence, ask how often the person on the receiving end would actually want this contact.

Good examples:

• Once for a single follow-up
• Daily for internal review tasks, routines, and consistent personal check-ins
• Weekly for customer care, reporting, and recurring touchpoints
• Monthly for maintenance, renewal prompts, and recurring updates
• Interval when the gap matters more than the weekday

If you are not sure, start less often than you think. It is easier to make an automation more active later than to rebuild trust after it becomes annoying.

Timezone matters more than people expect

Always set the right timezone. Automation feels smart only when it arrives at the right moment. A reminder at 8:00 AM in the wrong timezone is not a small mistake. It changes the experience completely.

This is especially important for:

• businesses with customers in multiple regions
• family schedules across time zones
• travel-related reminders
• appointments and check-ins

If the audience spans more than one region, decide whether the timing should follow your schedule or theirs.

Connectors: linking NetShow to the tools around it

Connectors give your automations somewhere to go. In the current connectors surface, NetShow recognizes integrations such as:

• Stripe
• Notion
• Telegram
• WhatsApp
• Discord
• Email
• Calendar
• Zapier
• Social Media

Each connector has a description and a status, which helps you understand whether it is only available or already connected. This is useful because a workflow without a connected destination is often just an idea waiting for an endpoint.

When to connect tools first

If your workflow depends on outside delivery, connect the relevant tools before you invest too much time in the automation itself. For example:

• connect email if reports must be mailed
• connect calendar if reminders depend on appointments
• connect social channels if content will be published
• connect Zapier if the final step needs another app

That way, you are not building an automation that reaches a dead end.

Social publishing as automation

A lot of users think of automation only in terms of reminders and tasks, but content publishing is automation too. Inside NetShow, the path from Content Studio into social management and scheduling is part of the larger operational system.

That means your process can look like:

1. Create content.
2. Review it.
3. Move it into social workflows.
4. Schedule or publish it through connected channels.

For a small business or creator, this may be one of the highest-value automation paths in the platform.

A simple automation you can build today

If you want a practical first automation, build this:

Weekly client check-in

1. Choose the agent who should handle the communication.
2. Open Schedule Builder.
3. Select the Weekly Check-in preset or create a custom weekly schedule.
4. Set the time and timezone.
5. Write a task description such as, “Check in with active clients and ask if they need anything this week.”
6. Save it.
7. Test one message before trusting the recurring version.

This one automation teaches the basics of timing, agent selection, task language, and review.

Writing better automation instructions

Your automation instructions should be specific, friendly, and outcome-focused. Bad automation instructions are vague. Good automation instructions tell the agent what matters.

Instead of:

“Follow up with leads.”

Try:

“Send a short, friendly follow-up to new leads asking whether they want to book a call this week. Keep it under 90 words and include our booking link.”

That level of clarity reduces weird outputs and makes the automation more consistent.

Pausing and adjusting live automation

Automation should never feel irreversible. If something is too frequent, mistimed, or poorly worded, pause it, adjust it, and resume it. The schedule system is built with statuses like pending and paused for exactly this reason.

You should pause an automation when:

• the message is wrong
• the timing is wrong
• the target audience changed
• the season or campaign ended
• the agent needs updated knowledge first

There is nothing wrong with turning an automation off while you improve it.

Common mistakes to avoid

The most common automation mistakes are usually simple:

• automating before the agent is well configured
• choosing the wrong channel
• scheduling too often
• using vague instructions
• forgetting the timezone
• not testing before going live

If you avoid those six mistakes, your automation experience gets much smoother very quickly.

How to test an automation safely

Before trusting an automation with real customers, use a test path:

• send the first message to yourself
• use internal or low-risk recipients first
• confirm the schedule fires when expected
• verify the wording matches your tone
• check any connected tools or channels

Think of this like testing a sprinkler before leaving it on all night. A small test up front saves a lot of cleanup later.

When to move from schedules to full workflows

At some point, simple timing stops being enough. That is usually your signal to graduate into workflows.

Move to full workflows when:

• you need multiple actions after one trigger
• you need branching logic
• you need data passed from one step to another
• you want richer orchestration than “send this at that time”

There is no downside to starting simple and moving up later. In fact, that is the cleanest way to learn the system.

A practical automation stack for most users

If you want a useful starting stack, use this combination:

• one schedule for reminders
• one daily or weekly check-in for proactive outreach
• one workflow for a multi-step recurring process
• one connector tied to where the results need to go

That gives you a meaningful automation layer without overwhelming your setup.

What to do next

If this is your first time using automation in NetShow, start with the easiest high-value win: a scheduled follow-up or weekly check-in. Once that works, connect the outside tool it depends on. After that, build one workflow that turns a repeated manual task into a reusable system.

That is how automation becomes trustworthy on NetShow. You begin with one real outcome, not a giant abstract system, and you let success stack from there.