Integration
Connect awork and GitHub
When New Client fires in awork, your agent runs Add Labels to Issue in GitHub, or New Branch in GitHub to Create Project Task in awork. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want awork and GitHub to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What awork and GitHub can do together
From awork to GitHub
When New Client in awork
then Add Labels to Issue in GitHub
From GitHub to awork
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with awork and GitHub
Triggers and actions 23 triggers · 40 actions
- New Client
Fires when a new company/client is created in awork. Poll/webhook on companies resource creation event.
- New Project
Triggers when a new project is created.
- New Task
Triggers when a new task is created. The trigger only fires for tasks with a project assigned, not for private tasks.
- New Time Entry
Triggers when a new time entry is created.
- Updated Client
Fires when an existing company/client is updated in awork. Poll/webhook on companies resource update event.
- Updated Project
Fires when a project is updated in the awork workspace.
- Updated Task
Triggers when a task is updated. The trigger only fires for tasks with a project assigned, not for private tasks.
- Updated Time Entry
Triggers when a time entry is updated.
- Create Client
Creates a client (company) in awork and returns the created company.
- Create Project
Creates a new project.
- Create Project Task
Creates a task in an awork project.
- Create Time Entry
Creates a time entry for a user, optionally against a project/task, using startDateUtc+duration or startDateUtc+endDateUtc.
- Delete Client
Deletes a client (company) in awork, optionally moving, detaching or deleting its linked projects and tasks.
- Delete Project
Deletes an awork project and its tasks, optionally deleting its time entries too.
- Delete Project Task
Deletes an awork task by id.
- Delete Time Entry
Deletes a time entry in awork.
- Find Project Tasks by criteria
Returns up to 100 tasks of a project that match the specified filter criteria.
- Find Time Entries by criteria
Returns up to 100 time entries in the workspace that match the specified filter criteria.
- Get Client by ID
Finds a client by id
- Get Project by ID
Finds a project by id
- Get Task by ID
Returns a single awork task (project or private task) by its id, including status, assignees, project, tags, lists and custom field values.
- Get Time Entry
Returns a single awork time entry by its id, including its task, project, user, type of work and breaks.
- Search Clients
Returns up to 100 clients (companies) whose name contains the specified text.
- Search Projects
Returns up to 100 projects whose name contains the specified text, optionally narrowed by an additional filter.
- Search Users by Email
Returns the awork users whose contact information includes the specified email address.
- Update Client
Updates an existing client (company) by ID. Fields left blank keep their current values.
- Update Project
Updates fields (name, status, workflow, etc) on an existing awork project.
- Update Project Task
Updates fields (name, status, assignee, due date, etc) on an existing awork task.
- Update Time Entry
Updates an existing awork time entry: its times or duration, type of work, project, task, note and billing flags.
- Issue Closed
Triggers when an issue in a repository is closed.
- New Branch
Triggers when a new branch is created in a GitHub repository.
- New Collaborator
Triggers when a new collaborator is added to a GitHub repository.
- New Commit
Triggers when a new commit is pushed to a GitHub repository's default branch.
- New Commit Comment
Triggers when someone comments on a commit in a repository.
- New Gist
Triggers when you create a new gist on GitHub.
- New Global Event
Triggers when a new public event happens anywhere on GitHub, such as a push, fork, or new issue.
- New Issue
Triggers when a new issue is created in a repository.
- New Label
Triggers when a new label is added to a GitHub repository.
- New Milestone
Triggers when a new milestone is created in a repository.
- New Pull Request
Triggers when a new pull request is opened in a repository.
- New Release
Triggers when a new release is published in a GitHub repository.
- New Repo Event
Triggers when new activity (pushes, issues, pull requests, releases and more) happens in a GitHub repository.
- New Repository
Triggers when a new public repository appears under a GitHub user or organization.
- New Watcher
Triggers when someone starts watching a repository.
- Add Labels to Issue
Adds labels to an issue or pull request in a GitHub repository, keeping its existing labels.
- Check Organization Membership
Checks whether a GitHub user is a member of an organization and returns true or false.
- Create Branch
Creates a new branch in a repository, starting from the commit you choose.
- Create Comment
Adds a comment to an issue or pull request in a GitHub repository.
- Create Gist
Creates a new gist with one file on the connected GitHub account.
- Create Issue
Creates a new issue in a GitHub repository.
- Create or Update File
Creates a new file in a repository, or replaces an existing file's contents, as a commit.
- Create Pull Request
Opens a pull request asking to merge one branch into another.
- Delete Branch
Deletes a branch from a repository. Any open pull request from that branch is closed.
- Find Branch
Finds a branch in a GitHub repository by name and returns its latest commit and protection status.
- Find Issue
Finds an issue in a GitHub repository by its number and returns its title, body, state, author and labels.
- Find Organization
Finds a GitHub organization by its login and returns its profile details.
- Find Pull Request
Finds a pull request in a GitHub repository by its number and returns its title, state, branches and merge status.
- Find Repository
Returns a GitHub repository by its owner and name, including its description, visibility, default branch and counts.
- Find User
Finds a GitHub user by username and returns their public profile.
- Get File Contents
Returns a file from a GitHub repository, with its base64-encoded content, at the default branch or a chosen branch, tag or commit.
- Submit Review
Submits a review on a pull request: approve it, request changes, or leave a review comment.
- Update Issue
Updates an existing issue in a GitHub repository, such as its title, text, state, labels or assignees.
- Update Pull Request
Changes a pull request's title, description, target branch, or open/closed state.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from awork
awork to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
awork to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
awork to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
awork to Google SheetsGoogle Sheets
awork to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
awork to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into GitHub
ActiveCampaign to GitHubActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to GitHubOrganize anything with Airtable, a modern database created for everyone.
Asana to GitHubAsana is a collaborative information manager for workspace.
ClickUp to GitHubClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to GitHubDiscord is an all-in-one voice and text chat for gamers.
Freshdesk to GitHubFreshdesk is a cloud-based customer support and helpdesk platform.
Questions
awork and GitHub, answered
What can start an automation from awork?
Any of awork's 8 triggers in the catalog, including New Client, New Project, New Task and New Time Entry. Describe the moment in plain language and your agent picks the right one.
What can your agent do in GitHub when something happens in awork?
Any of GitHub's 19 actions, including Create Branch, Create Comment, Create Gist and Create Issue. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from GitHub to awork?
Yes. When something happens in GitHub, your agent can act in awork too. This page covers both directions: GitHub's triggers and awork's actions are listed here as well.
Do I have to build a connector for awork or GitHub?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.