Link your accounts once — then read, send and automate across them from inside Atwork, with your own sign-in and nothing to host.
Each integration brings real triggers and actions into your workspace — here's exactly what each one can do.
Connect your bot once and your workspace can talk — send messages, photos and documents to any chat, add tappable buttons, and react the moment someone writes back or presses one.
Connect your bot once and your workspace can talk — send messages, photos and documents to any chat, add tappable buttons, and react the moment someone writes back or presses one.
A message arrives · A button is pressed · Send a message · Send a photo · Send a document · Reply to a button press
A client taps “Approve” under the quote your workflow sent — and the deal moves to the next stage before you've switched apps.
Your team's channels become part of the workflow: post and update messages, open channels, react — and start workflows from new messages or reactions.
A new message is posted · A reaction is added · Send a message · Update a message · Create a channel · Add a reaction · Read channel history
A ✅ reaction on the launch thread marks the task done in Atwork — the team never leaves Slack, the board stays true.
Connect any inbox over IMAP and send through SMTP. Incoming mail becomes structured, trackable work; outgoing mail comes from your own address.
An email arrives · Send an email
A request lands in support@ — it becomes a ticket row with the sender attached, and the acknowledgment goes out before anyone opens the inbox.
Publish to your LinkedIn from the workspace — posts with images, straight from the content row your team already reviewed.
Publish a post (with image)
The content calendar hits Friday, the post goes live on LinkedIn, and the row keeps the link — publishing without the copy-paste ritual.
Two-way sync with Google Calendar. Events you create or move in Atwork show up in Google, and changes made in Google flow back.
Create an event · Update an event · Keep calendars in sync
A booking confirmed in Atwork appears in your Google Calendar seconds later — and moving it there moves it back.
Google Meet, Zoom and Microsoft Teams links, minted where the meeting is planned — no tab-hopping to create a room.
Create a meeting link · Remove a meeting link
The intro call gets scheduled and the Zoom link is already on the invite — created by the same workflow that booked the slot.
Atwork lives inside your Zaps and Make scenarios too. React when something changes in your sheets, or create and update work from thousands of other apps — whichever platform your team already automates with.
Something changes in Atwork · Create or update items
A Stripe payment lands in your Zap — and the customer's row in Atwork flips to Paid, kicking off the delivery workflow.
Choose the tool in your workspace settings and sign in with your own account — OAuth where the service supports it.
The connection shows up as triggers and actions on the automation canvas, and in the surfaces that use it — email wizard, calendar, booking.
Connections belong to your workspace, can be reconnected or removed any time, and everything they do lands in your activity history.
Every trigger and action you just saw plugs into the workflow builder — drawing the flow is the easy part.
Explore Automation →More on connecting your tools to Atwork
Seven Atwork workflow recipes that turn emails into tasks automatically: support triage, auto-replies, lead capture, invoice routing, VIP escalation, and more.
Atwork speaks MCP, so Claude can read your sheets and create tasks directly. What it can do, what it cannot, and when this beats using an in-app agent.
Build a custom AI agent in Atwork, scope what it can see, assign it tasks like a colleague, and @mention it in comments. A practical setup guide.