Skip to main content

What are Automation, Reports, and Workspaces?

An overview of the Automation tab in Teamline, explaining what Workspaces and Reports are, how automation works, and how teams run standups, meetings, and surveys via Slack or Microsoft Teams

Vlad avatar
Written by Vlad
Updated over a week ago

Automation is one of the core tabs in Teamline.


This is where teams automate standups, meetings, check-ins, and surveys - and make sure they happen consistently, without manual coordination.

From a business perspective, Automation exists to replace recurring meetings and follow-ups with structured, predictable workflows that run on their own.


What is Automation?

Automation is the system that runs your recurring team rituals:

  • Daily or weekly standups

  • Async meetings

  • Blockers checks

  • Planning prompts

  • Team surveys and pulse checks

Instead of scheduling calls or chasing updates, Teamline automatically reaches out to people, collects responses, and delivers structured results.

Automation can be used:

  • With JIRA - to connect updates directly to tasks

  • Without JIRA - for team check-ins, surveys, or meetings

The key requirement for Automation is a connection to a business messenger.


What is a Workspace?

A Workspace is the foundation of Automation in Teamline.

It represents the space where your team communicates:

  • In Slack - a Slack workspace

  • In Microsoft Teams - a Team (within MS Teams)

Teamline connects to these workspaces and uses them as the source of participants for reports.

In simple terms:

If a person exists in the connected workspace, they can participate in reports.


What is a Report?

A Report is the actual automation you create and run in Teamline.

Each report represents one automated workflow - for example:

  • A daily standup

  • A sprint check-in

  • A retrospective survey

  • A planning or estimation round

Reports define what happens, when it happens, and who participates.


How a Report is structured

Each report consists of three main parts.

1. Schedule

This defines when and how often the report runs.

Here you configure:

  • Start time

  • Time zone

  • Frequency (daily, weekly, custom)

The schedule ensures your automation runs consistently, without manual triggers.


2. Respondents

This is the core of the report.

  • Selected from users in the connected workspace

  • Can be individuals or groups

  • Define who receives the report and responds

Questions

Questions are fully customizable.

Teamline supports different question types:

  • Text response
    Users provide a free-form written answer.

  • Single-choice / Multi-choice survey
    You define the answer options, users select from them.

  • Task response (JIRA / Trello)
    Users select tasks from a connected task tracker.
    Which tasks are shown is controlled by admin-defined rules.

Templates provide default questions, but every question can be edited, replaced, or customized to fit your process.


Waiting time

Waiting time defines how long the report stays open for responses.

For example:

  • Report starts at 10:00 AM

  • Waiting time = 30 minutes

  • Report closes at 10:30 AM


3. Result delivery

Once the report is completed, Teamline delivers the results automatically.

Delivery options include:

  • Direct messages

  • Channels or group chats

  • Email

  • AI whiteboard

  • Webhooks (for example, Google Sheets or other systems)

This allows results to reach exactly the right audience - without manual sharing.


Why this model works

By combining Workspaces and Reports, Teamline creates a system where:

  • Automation runs where people already communicate

  • Participation is effortless

  • Results are structured and actionable

  • Meetings become optional, not mandatory

Automation turns recurring team rituals into reliable, low-friction workflows - helping teams stay aligned without slowing down.

Did this answer your question?