Skip to content
Hypamoon

Work and projects

Connect awork to Hypamoon

Yes. awork has a public, versioned API and you create the key yourself, so your chat can write the adapter.

Open

The check

Three questions about the API of awork, answered from its own docs.

Public API docs
Yes. Public developer portal with API reference and guides. Read the docs
A key you create yourself
Yes. An admin generates a long-lived API key under Settings, Integrations; OAuth client applications are created there too. developers.awork.com
Versions or a changelog
Yes. Dated changelog that marks breaking changes, and versioned paths (/api/v1). developers.awork.com
How it signs in
A long-lived API key as a bearer token with admin-level access, or OAuth 2.0 for user-specific tokens.
Webhooks
Yes. It can tell your app when something changes. developers.awork.com
Hosting
Cloud

Your own project overview on awork, for clients and the team.

  • Projects, tasks, time entries and users from awork.
  • AI that spots tasks past their due date and people with too much planned.
  • A screen for your clients and a weekly email for you.

Ask your chat

Answers straight from your awork data, in Claude or another chat with the full Hypamoon connection.

  • Which tasks are past their due date in each project?
  • Who has more hours planned this week than available?

When something happens

awork sends a webhook to your app, and the app asks AI what happens next.

  1. When

    A task changes status in awork.

    AI decides

    AI decides whether the client should hear about it.

    Then

    The project lead gets an email with a short update to pass on.

A screen for your team or customers

An app on your own address, with sign-in, on top of the same awork data.

  • For your customers

    Clients sign in and see the status of their own projects and the next milestones.

awork stays the core: your chat builds the rest on its API, as an adapter plus an app and agents in your Hypamoon project. Reading starts after you click Allow in the portal. Every change an agent or a chat makes in awork waits for your approval, one call at a time. How adapters work

Good to know

  • Your adapter uses a fixed key: you paste it once in the Hypamoon portal, never in the chat, and it only goes to the API host you allow.
  • Up to 50 requests per second and 1,000 per minute (3,000 on Enterprise), shared by all client applications in a workspace.

Try it in your chat

Fill in what to read and write, and send it.

Say this in your chat

Build the Hypamoon recipe build-an-adapter for awork. API docs: https://developers.awork.com/. Read: [what]. Write: [what, or nothing].

In Claude, or another chat with the full Hypamoon connection; adapters are not in ChatGPT yet. You paste the key in the portal, never in the chat. The full recipe

Sources

Checked on 7 November 2026.

awork is a name of its owner, used here only to describe the software. This page is not an official integration and Hypamoon has no partnership with awork. Found something that changed? Tell us at support.

Tool not listed? Ask the chat to check its API.

The same three checks work for any software. Your chat reads the vendor's own docs and tells you what it found.

Say this in your chat

Check if [software] has an open API that a Hypamoon adapter can use: public API docs, a key or token I can create myself without asking the vendor, and versions or a changelog. Link the pages you used.

Fill in the name of your software. Checking needs no connection to Hypamoon.

Ready to connect awork?

Connect your chat once, then ask it to build the adapter.

Works in Claude, ChatGPT and Copilot. Add to Claude Add to ChatGPT Add to Copilot