Skip to content
Notis

Connect Outlook to Chatwork

When something happens in Outlook, Notis takes the next step in Chatwork. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Examples

Ways Notis can move work from Outlook to Chatwork

View example

Check Chatwork context for every new Outlook email

When an Outlook email arrives, retrieve relevant recent Chatwork messages so the assistant can prepare a context-rich triage brief.

View example

Add Chatwork status to new Outlook email triage

Use the Chatwork status endpoint alongside each new Outlook email to identify unread pressure and outstanding tasks before prioritizing.

View example

Review Chatwork rooms when a calendar event is created

When a new Outlook calendar event appears, retrieve Chatwork rooms so the assistant can identify the right collaboration space and preparation context.

View example

Identify Chatwork members for a new Outlook meeting

For each new Outlook calendar event, retrieve members from a named Chatwork room to support attendee and preparation checks.

View example

Review Chatwork context when an Outlook event changes

When an Outlook calendar event is created, updated, or deleted, retrieve relevant Chatwork messages to assess coordination impact.

View example

Check Chatwork workload after an Outlook calendar change

After an Outlook calendar change, retrieve Chatwork status to show whether the new schedule collides with current unread and task pressure.

View example

Review Chatwork threads after sending an Outlook message

After an Outlook message is sent, retrieve relevant Chatwork messages to confirm alignment and identify unanswered coordination points.

View example

Find a Chatwork room for a sent Outlook update

When an Outlook message is sent, retrieve Chatwork rooms and recommend where the update belongs for later coordination.

View example

Check Chatwork contacts when an Outlook contact is added

When a new Outlook contact is created, retrieve Chatwork contacts to identify an existing match and prevent duplicate outreach records.

Supported Triggers and Actions

Notis builds workflows that link Outlook to Chatwork. A trigger fires from one place; an action lands in another.

Outlook triggers

Chatwork actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Delete Message

This tool allows you to delete a specific message from a chatwork room by calling the delete endpoint at https://api.chatwork.com/v2/rooms/{room id}/messages/{message id}. it requires authentication using a chatwork api token provided in the x-chatworktoken header, and the necessary permissions to delete messages in the specified room.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Get Chatwork Contacts

This tool retrieves a list of all contacts from chatwork. it is a fundamental tool that fetches all contact information such as account id, room id, name, chatwork id, organization details, department, and avatar image url, without needing additional parameters beyond authentication.

ActionInstant

New Contact Added

Triggered when a new contact is added in the Outlook contacts.

TriggerInstant

Get Chatwork File

This tool retrieves information about a specific file in a chat room. the api endpoint get /v2/rooms/{room id}/files/{file id} provides file details such as file id, account id, message id, filename, filesize, upload time, and download url, which are useful for retrieving file metadata, verifying file existence, and managing file sharing within chatwork.

ActionInstant

Calendar Event Changes

Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.

TriggerInstant

Get My Chatwork Status

This tool retrieves the current status of the authenticated user, including unread message counts and task status. it provides a quick overview of unread messages, mentions, and tasks, making it valuable for monitoring chatwork activity and building automation workflows.

ActionInstant

New Calendar Event

Triggered when a new calendar event is created in the Outlook calendar.

TriggerInstant

Get Room Members

This tool retrieves a list of all members in a specified chatwork room using the endpoint get /rooms/{room id}/members. it provides essential details like account id, role, name, chatwork id, organization id, and organization name, complementing the existing suite of room management tools.

ActionInstant

New Outlook Message

Triggered when a new message is received in the Outlook mailbox.

TriggerInstant

Get Room Messages

This tool retrieves messages from a specific chatwork room using the get https://api.chatwork.com/v2/rooms/{room id}/messages endpoint. it requires a room id parameter and an optional force flag to refresh the cache by retrieving the 100 newest messages.

ActionInstant

New Sent Message

Triggered when a new message is sent from the Outlook mailbox.

TriggerInstant

Get Chatwork Rooms

This tool retrieves a list of all chat rooms associated with the authenticated chatwork account. it includes group chats, direct chats, and personal chats, and does not require any additional parameters beyond authentication.

ActionInstant

Upload File to Chatwork Room

This tool allows users to upload files to a specific chatwork room. it enables file sharing functionality within the chatwork platform by providing an endpoint to upload files (along with an optional message) to a given room.

ActionInstant
Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event
Works with
ZapierPipedream
Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only
Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match
Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation
Cost
$ · pay per run
$$ · AI models per run
Reliability
Breaks on schema change
Adapts to format changes
Setup
Click 8 dropdowns
Describe it in English
Handles fuzzy
Hard-coded fields only
Reads intent, summarises
Human in loop
Bolted on
Built in · approval inbox
Maintenance
You own every break
Self-heals · we own it
Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

Notis

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"
Condition✦Status = "Blocked"
AI step✦Summarise the blocker in plain English
ActionDM the row owner with summary
Timeout✦No reply in 24h → ping you
Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.

  • Full run history with inputs, outputs and traces
  • Replay any run with edited inputs
  • Approval inbox, confirm via chat in one tap
  • Audit logs for compliance teams

Automations

Inbox

All12Manager5Telegram1Messages0Whatsapp2Email4Slack8

Migrate background jobs to a durable queue You can cancel it through Stripe

3 days

Notis v3 release update This one’s v3: Notis Manager (desktop app with …

8 days

Add multi-tenant RBAC User initiates a voice call

13 days

Draft pricing v (tiers, limits, overages) and sanity-check margins

2 weeks

Verify analytics events for new features That’s a really interesting automat…

1 month

Everything in the box.

Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.

AI in the middle

Every step can include an LLM call: summarise, classify, extract, rewrite.

Full observability

Every run, every step, every input, all replay-able from Mission Control.

Human in the loop

Pause for approval. Notis pings you in chat with one-tap approve.

Self-healing

When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.

Related pairs

More ways to connect Outlook and Chatwork

Connect any two apps with Notis in the middle.

Outlook and Chatwork, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Chatwork.