# awork integrations: projects and tasks

> Create a project, create a task and create a time entry in awork, and start a workflow when awork sends “Project added”.

**Canonical page:** https://tray.ai/connectors/awork-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

awork is a work management tool for agencies and teams that plans projects and tasks, tracks time, and shows team workload in one workspace. Tray.ai connects to awork through the HTTP Connector, so your workflows can call the awork API alongside the rest of your stack.

## Use cases

### Projects

Read, create, update, and delete projects in awork from any Tray.ai workflow. The awork API covers calls such as list projects and create a project.

- List projects
- Create a project
- Update a project

### Tasks

Read, create, update, and delete tasks in awork from any Tray.ai workflow. The awork API covers calls such as create a task and get a task.

- Create a task
- Get a task
- Update a task

### Time entries

Read, create, and delete time entries in awork from any Tray.ai workflow. The awork API covers calls such as list time entries and create a time entry.

- List time entries
- Create a time entry
- Delete time entries

### Companies

Read, create, update, and delete companies in awork from any Tray.ai workflow. The awork API covers calls such as list companies and create a company.

- List companies
- Create a company
- Update a company

### Webhooks

Read, create, update, and delete webhooks in awork from any Tray.ai workflow. The awork API covers calls such as list webhooks and create a webhook.

- List webhooks
- Create a webhook
- Update a webhook

### awork events

Start a Tray.ai workflow the moment something happens in awork. awork sends events such as project added and project status changed to a Tray.ai webhook trigger.

- Project added
- Project status changed
- Task added

## Challenges Tray.ai solves

### Keeping awork credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store awork credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the awork API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the awork API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to awork?

Yes. Tray.ai connects to awork through the HTTP Connector, which calls the awork API directly. Any call the awork API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with awork?

The awork API uses a bearer token and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated awork connector?

awork runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated awork connector from the awork API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/