100 things your AI employees can do on day one

The employee reads new mail on a schedule and sorts it with real Gmail labels, so the triage is visible in the client you already use.

GmailMailbox

It searches how you answered similar threads before, then leaves a Gmail draft for you to send.

GmailMailbox

An overnight scheduled job labels and files in batches, and reports what it could not decide.

GmailMailbox

Matching mail gets a label you choose and a task in review, so nothing sensitive is answered automatically.

GmailMailbox

It reads the whole thread and writes the summary back as a draft or a task.

GmailMailbox

A daily job searches for sent mail with no reply past your cutoff and drafts the nudge.

GmailScheduled Jobs

It labels the thread and posts the handoff into the Slack channel that owns it.

GmailSlackMailbox

A job on your morning cron reads overnight mail and writes one summary you can read in a minute.

GmailScheduled Jobs

A single `calendar_find_free_time` call does the intersection, so it does not degrade as you add people.

Google CalendarChat

A morning job reads the day’s events and files a brief per external attendee.

Google CalendarDocuments

The brief is assembled from your own CRM contacts, deals and logged activity, which needs nothing connected.

Google CalendarCRM

Upload the recording, it is transcribed and diarized, and the employee writes the summary and proposes owned action items.

Proposed action items are reviewed on the meeting page and become real tasks when you accept them.

A daily job reads tomorrow’s events and drafts an agenda to the attendee list.

Google CalendarGmailScheduled Jobs

It compares the invite list to who spoke in the transcript and drafts the catch-up note.

Google CalendarGmailMeetings

Tell it the new arrival time and it moves each affected event and notifies the attendees.

Google CalendarChat

It books the blocks as real events, so anyone checking your availability sees them.

Google CalendarChat

The employee searches the web, writes the brief into Documents and links it to the CRM record.

Web research writes straight back to the contact and organization records.

It drafts from the brief it just wrote, so the specific detail comes from research rather than a merge field.

The CRM is part of Tenfold, so activity logging is native and needs nothing connected.

It updates the deal from what actually happened in the thread or the call.

A weekly job compares last logged activity against your cycle length and raises the stale ones.

Templates live in Documents, so the draft starts from your approved language rather than the model’s.

Each employee has its own real email address, and answers from your pricing docs.

A job reads your deals and writes the review up, ready to open.

The recap is drafted from the transcript as soon as it is processed.

GmailMeetings

Your docs are indexed and searchable, so the answer is quoted from them rather than recalled.

The reply is held for approval instead of sent, and the thread is raised for review.

It detects the language of the incoming message and answers in it.

A resolved thread becomes a draft document in the folder you nominate.

A weekly job clusters recent threads and opens one task with the examples attached.

The mailbox is answered by an employee that does not keep hours.

It looks the sender up in your CRM first and refuses when the details do not match.

Your policy document sets the bounds, and anything past them is held for approval.

It posts the update to the channel and keeps the same message current as things change.

SlackChannels

A weekly job reads the week’s threads and reports themes rather than counts.

Upload the recording, and the transcript becomes drafts across Documents, the Composer and the social calendar.

The employee proposes posts against your pillars and fills the calendar, for you to approve.

It researches the topic and writes the metadata alongside the draft.

Knowing which content performed needs your analytics. The repurposing itself does not.

Google AnalyticsComposer

A scheduled job reads mentions and raises only the ones that need a person.

XSocial Desk

Drafts sit on the calendar until you approve them, then publish to the connected channel.

LinkedInXSocial Desk

It works from the meeting transcript, so the quotes are things the customer actually said.

Brand voice and content pillars are saved once and read by every employee that writes.

Name the competitors once, and a weekly job researches and reports what changed.

It drafts the variants, and your email platform runs the split and returns the result.

MailchimpChat

A scheduled job finds invoice mail, reads the amounts and appends a row per line item.

GmailGoogle SheetsChat

It reconciles the two lists and reports only the transactions with nothing attached.

QuickBooksGmailChat

A daily job reads what is outstanding and drafts the next note in the sequence.

QuickBooksGmailScheduled Jobs

It reports what did not match, not what did.

QuickBooksChat

It reads your existing categories and applies them, holding anything ambiguous for you.

QuickBooksChat

The checklist is a project of real tasks with owners, rebuilt each month by a scheduled job.

It fills your PO template from the request and files the draft for signature.

A daily job compares spend to budget and posts when you cross the threshold you set.

QuickBooksSlackScheduled Jobs

It reads the contracts in your Documents and opens a task ahead of each renewal window.

A Monday job reads the numbers and writes the page before you are up.

QuickBooksScheduled Jobs

The requirements live in a document, and each application is scored against them with the reasoning shown.

It works from the roles you have already written, so the new one sounds like your company.

It finds the shared availability and books the whole loop in one pass.

Google CalendarChat

Each scorecard is generated from that role’s requirements, so interviewers rate the same things.

The recruiting employee has its own address and answers from your hiring docs.

Each note references the actual application, and you can hold them all for approval.

The checklist is a workflow with approval gates, so it runs the same way every time.

The handbook is indexed, and answers quote the section they came from.

A monthly job reads the records and opens a task before each expiry.

It builds the packet from your templates and sends it for signature.

A cron you choose runs the job, and the finished write-up arrives as a card in your channel.

SlackScheduled Jobs

It reads each source through its connector and writes the reconciled view to one sheet.

Google SheetsChat

It works on a copy and reports every change, so you can check before you keep it.

Google SheetsChat

Uploaded PDFs are parsed and indexed, so you can ask across them instead of opening each one.

The job checks on your interval and stays quiet until the threshold is crossed.

SlackScheduled Jobs

It reads the numbers first and writes around them, so there are no blanks to chase.

Google SheetsScheduled Jobs

A scheduled job sweeps your CRM and reports what is incomplete or untouched.

A job reads both sides on a schedule and writes the differences across.

HubSpotGoogle SheetsScheduled Jobs

Steps are durable and approval gates pause the run, so a restart does not redo finished work.

It writes the procedure up and saves it as a skill any employee can reuse.

A morning job groups the noise and reports what is new or growing, not what is loudest.

SentryScheduled Jobs

It reads each new issue, applies your labels and assigns from your own routing rules.

LinearChat

It reads the diff and leaves the obvious findings, so the human review starts further along.

GitHubChat

It correlates the deploy with what changed and posts the summary to on-call.

GitHubSlackScheduled Jobs

It compares merged changes against the runbook and drafts the edit.

GitHubDocuments

Access docs are indexed, and the answer cites the page it came from.

A workflow with approval gates does the steps in order and records each one.

OktaWorkflows

It reads the timeline and writes the draft, leaving the causes for the humans.

PagerDutyDocuments

A weekly job matches new advisories against what you actually depend on.

GitHubScheduled Jobs

Everything you upload is indexed, and answers cite the document they came from.

Skills and document access are set per employee, so scope is a configuration and not a prompt.

Each employee keeps its own durable memory, so a decision survives the end of the conversation.

Every run leaves a work log entry and a reviewable deliverable.

Ask returns the answer and the source, rather than ten links to read yourself.

Ask it to compare a set of documents and it reports where they disagree, with both quotes.

A patient employee with your handbook, that never makes anyone feel slow for asking twice.

Describe how the job is done once and it is saved as a skill, not retyped into every prompt.

Scheduled jobs run in your timezone whether or not anyone is signed in.