Automate repetitive marketing tasks

Automate the work that comes back on a predictable rhythm, starts from the same places each time, and ends with a result someone uses. If you can describe the job in two or three sentences and you'd hand it to a capable new hire without much worry, it's a good candidate.

These are the recurring jobs teams most often hand to Kite:

• A weekly performance report. Kite compares last week's traffic, top pages, sources, and conversions with the week before, explains what changed and why, and suggests what to do next.
• A competitor check. Kite looks at competitors' websites, pricing pages, current ads, and recent news, then tells you what's new and whether it calls for a response.
• Lead follow-up. When someone fills in a form, Kite researches the person and their company, compares them with your ideal customer, drafts a reply with a next step, and records the lead in your CRM.
• A content refresh. Once a month, Kite checks which of your pages are losing search rankings or traffic and rewrites the sections that have fallen behind.
• A social posting rhythm. Kite drafts the week's posts from your latest launch, article, or results, with suggested timing.

Some work suits automation less well. A positioning change, a pricing decision, or a launch plan depends on context only you have, so it's better as a conversation with Kite than a scheduled job.

You don't have to come up with the list yourself. After Kite delivers something you'd probably want again, such as a report or a competitor check, it may offer to put it on a schedule.

You set up a recurring job by telling Kite what it should do, in the same words you'd use with a colleague. For example, you might write, "Every Monday at 9, compare last week's site traffic and signups with the week before and tell me what changed and why." Kite saves the instruction for the job separately from the timing, so each run simply does the work that's due.

Before it saves a workflow, Kite checks that the apps the job needs are connected. A report on your HubSpot pipeline needs HubSpot, for example, while a report on a website Kite hosts needs nothing extra, because Kite already tracks that site's traffic and conversions.

Some recurring work has to sign in to a website that doesn't offer a connection, such as a partner portal you export a report from. In that case, Kite opens the login page and sends you a link so you can sign in once while you're present. It saves that login with the workflow, and later runs reuse it without stopping at the login screen.

When the job is a process you care about getting exactly right, such as the structure of a newsletter or the steps of a competitor review, you can also save it as a custom skill. A skill holds the reusable instructions for the job, so Kite follows the same process on every run while it adapts the content to what it finds.

Related How-to pages

• How to save a repeatable marketing process as a skill your AI agent follows Coming soon Turn a process you repeat, like a weekly newsletter or a competitor review, into instructions Kite follows the same way every time.

A scheduled job runs at the times you name, in your own time zone. You can ask for every weekday at 8 a.m., every Monday at 9, the first of each month, or every half hour. Kite keeps the job on your local time when the clocks change for daylight saving.

A schedule has to land on fixed days or times, so "every other week" isn't something Kite can set up. When you ask for one, Kite says so and offers a fixed weekday or a monthly date instead.

A schedule works best when the work is due whether or not anything happened, like a Monday report your team reads before its weekly meeting. If a report needs more room than a chat message, Kite can publish it as a dashboard at a stable link that Kite updates each time the report runs.

Some work should start the moment something happens rather than at a set time. For those jobs, Kite gives the workflow its own web address, called a webhook, which another tool calls to start a run. Whatever that tool sends along, such as the name, email, and company someone typed into your form, becomes the details Kite works from on that run.

Almost any tool can call the address:

• Your website's form. The form's handler sends each submission to Kite.
• A form tool. Typeform, HubSpot forms, Tally, or a Google Apps Script can send each new response to Kite.
• An analytics or automation tool. PostHog, Segment, or Zapier can forward a chosen event, such as a new signup or a trial that's about to end.

Here's what a lead follow-up looks like. Someone requests a demo on your website, and the form sends their details to Kite. Kite researches the person's role and company, compares them with your ideal customer, and drafts a reply that proposes a sensible next step. It records the lead in your connected CRM and tells your team about it. The reply goes out once it's approved, or right away if you've given Kite permission to send these on its own.

The workflow sits idle until something calls the address, and Kite tells you so when it sets the job up. Treat the address like a password, because anyone who has it can start a run.

Some recurring checks only matter when something changes. If you add Kite to Slack, you can set up a standing watch, and Kite checks on a schedule but stays quiet until it finds something worth telling you about.

A watch can follow your website's traffic, a specific web page such as a competitor's pricing page, a Slack channel, or a web search. It can also look for mentions of your brand, news about your prospects, competitor launches, and new public reviews. Kite checks no more often than once an hour and reports in the Slack thread where you asked for the watch. For a new team, Kite can start a few watches itself, such as one on your traffic, one on your brand, and one on each competitor your website compares itself with. It tells you why each one exists and how to stop it.

The difference from a scheduled job is what happens when nothing changes. A weekly report arrives every week, even when the week was quiet. A watch on a competitor's pricing page only speaks up when the page actually changes.

Each workflow delivers its results to a place you choose. If your team uses Slack, that can be the thread where you set the job up, your team's main channel, or another channel you name. Without Slack, Kite emails each result from your team's Kite address to the person who set up the workflow, and replying to that email continues the conversation. You can also keep a job's results inside Kite, where each run appears as its own conversation in the Kite web app. A job whose purpose is to update another system, such as adding leads to your CRM, doesn't need to post anywhere.

Automated work follows the same approval rules as work you ask for in person. By default, Kite asks before it publishes a webpage, sends an email, or posts on social media, and it brings the draft to you with Approve or Publish buttons. That means you can automate a monthly content refresh and still read each rewritten page before it goes live. When you trust a job enough, you can give Kite more autonomy so the work runs end to end.

Kite keeps a list of your team's workflows, including paused ones, and you manage them by asking. You can ask Kite to show what's scheduled, move a report from Monday to Tuesday, change what a job covers, or send its results somewhere else. Kite updates the existing workflow rather than creating a second one, so its history stays in one place.

You can also run any workflow right now, which is handy when you want to see a sample before the first scheduled run. Running it early doesn't change its schedule. Pausing a job stops both its schedule and its webhook, and deleting it removes it entirely.