AWORK n8n INTEGRATION: AUTOMATE AWORK WITH N8N

This action retrieves all documents associated with a specific project in Awork, making it perfect for building workflows that need to process, backup, or sync project documentation automatically. Whether you're creating a document audit trail or migrating files to another platform, this action gives you programmatic access to your project files.

Key parameters: The action requires your Awork account credentials for authentication and a Project ID to specify which project's documents to retrieve. The Project ID field accepts text input and supports JavaScript expressions using {{ }} notation for dynamic values.

Use cases: Automatically backup project documents to Google Drive when a project is completed, generate a document inventory report for compliance purposes, or sync project files across multiple platforms when new documents are added.

This action retrieves a specific document from Awork using its unique identifier. It's particularly useful when you need to access document details or content as part of a larger automation workflow, such as processing a specific file mentioned in a notification or pulling document metadata for reporting.

Key parameters: This action requires your Awork credentials and a Document ID field where you enter the unique identifier of the document to retrieve. The Document ID accepts text input or JavaScript expressions within {{ }}.

Use cases: Fetch document details when a specific file is referenced in another system, retrieve document metadata for audit logging, or access document information to populate templates or reports.

This action creates a new document within a specified document space in Awork. It's essential for workflows that need to automatically generate documentation, create meeting notes, or establish project artifacts without manual intervention.

Key parameters: The action requires a Document Space ID where the new document will be created, and a Document Name for the title. Optional parameters include Project ID to associate the document with a specific project, an Emoji visual identifier, and a Parent Document ID if you want to nest this document under an existing one.

Use cases: Auto-generate project kickoff documents when new projects are created, create meeting notes templates when calendar events are scheduled, or establish standard documentation when onboarding new clients.

This action retrieves the actual content of a specified document from Awork. Unlike getting document metadata, this action fetches what's inside the document, making it valuable for content processing, analysis, or migration workflows.

Key parameters: This action requires your Awork account credentials and a Document ID field to specify which document's content to retrieve.

Use cases: Extract document content for analysis or reporting, migrate document content to another documentation platform, or process document text for search indexing or summarization.

This action retrieves all documents within a specific document space in Awork. Document spaces help organize your documentation, and this action lets you programmatically access everything within a particular space for bulk operations or synchronization.

Key parameters: The action requires your Awork credentials and a Document Space ID field that accepts text or expression input to identify which document space to query.

Use cases: Sync all documents from a document space to an external storage system, generate inventories of all documentation within specific spaces, or trigger notifications when document counts exceed thresholds.

This action retrieves all documents across your entire Awork account. It's the broadest document query available, useful for comprehensive audits, backups, or when you need a complete picture of your documentation landscape.

Key parameters: This action requires your Awork account credentials. The Resource parameter is set to 'Document' and the Operation is set to 'Get All Documents'.

Use cases: Create complete documentation backups on a scheduled basis, generate organization-wide document reports, or audit document creation and modification patterns.

This action retrieves detailed information about a specific company in Awork using its unique identifier. Perfect for workflows that need to access company data when processing deals, generating reports, or syncing customer information across platforms.

Key parameters: The action requires your Awork credentials and a Company ID field that supports text input and JavaScript expressions to identify which company to retrieve.

Use cases: Fetch company details when processing sales opportunities, populate templates with company information for proposals, or sync company data changes to your CRM or accounting software.

This action creates a new company record in Awork. Essential for workflows that onboard new clients, sync company data from other systems, or automatically establish company records based on external triggers.

Key parameters: The required parameter is Company Name. Optional parameters include Company Description for additional details and Company Industry to categorize the company.

Use cases: Automatically create company records when new deals are won in your CRM, sync company data from your accounting software to Awork, or establish client records when new contracts are signed.

This action retrieves all companies from your Awork account with powerful filtering and sorting options. Ideal for generating reports, syncing company directories, or building dashboards that display company information.

Key parameters: The action includes a Return All toggle to choose whether to return all results, a Filter By field for applying conditions using expressions, and an Order By field for sorting results.

Use cases: Generate company reports filtered by specific criteria, sync your complete company directory to external systems, or build dashboards showing company distributions by industry.

This action retrieves user details based on a specified user ID. Useful for workflows that need to access user information for assignments, notifications, or when processing user-specific data.

Key parameters: This action requires your Awork credentials and a User ID field that accepts text or expressions to identify which user to retrieve.

Use cases: Fetch user details to personalize notification messages, retrieve user information when processing task assignments, or access user data for reporting or audit purposes.

This action retrieves all comments associated with a specific project task. Perfect for workflows that need to aggregate feedback, sync discussions to other platforms, or trigger actions based on comment activity.

Key parameters: The action requires your Awork credentials, with the Resource parameter set to 'Project Task' and Operation set to 'Get Comments'.

Use cases: Sync task comments to Slack channels for team visibility, archive task discussions when projects are completed, or trigger notifications when new comments meet specific criteria.

This action retrieves all users from your Awork account with filtering and sorting capabilities. Essential for user management workflows, team reporting, or syncing user directories across platforms.

Key parameters: The action includes a Return All toggle, a Filter By field for applying user criteria, and an Order By field for sorting users by specified fields.

Use cases: Sync user directories between Awork and your HR system, generate team reports or organizational charts, or audit user accounts and permissions.

This action adds an existing task to a specific task list within a project. Useful for organizing tasks into categories or moving tasks between lists based on workflow stages.

Key parameters: The action requires a Project ID to identify the project containing the task list, and a Task List ID to specify which list to add the task to.

Use cases: Automatically organize tasks into appropriate lists based on criteria, move tasks between lists when status changes, or batch organize tasks during project restructuring.

This action creates a new type of work for project tasks in Awork. Work types help categorize tasks and are useful when you need to dynamically establish new categories based on project requirements.

Key parameters: The required parameter is Name for the work type. An optional Icon parameter allows you to specify a visual representation for the work type.

Use cases: Create new work types when new project categories are established, dynamically generate work types based on client requirements, or sync work type categories from project management templates.

This action adds a comment to a specific project task in Awork. Essential for workflows that need to log activity, provide automated updates, or sync discussions from other platforms.

Key parameters: The action requires a Task ID to identify which task to comment on, and a Comment Message field that accepts fixed text or expressions for the comment content.

Use cases: Automatically log status updates from external systems as task comments, add automated progress notes when milestones are reached, or sync comments from support tickets to related tasks.

This action assigns a task to a specific user within a project. Perfect for automated task distribution, load balancing, or routing tasks based on skills, availability, or other criteria.

Key parameters: The action requires a Task ID to identify which task to assign, and a User ID to specify which user should be assigned the task.

Use cases: Automatically assign tasks based on team member availability, route tasks to appropriate team members based on skill matching, or reassign tasks when team members are out of office.

This action retrieves all task lists associated with a specific project. Useful for understanding project structure, building project overviews, or syncing task list information across platforms.

Key parameters: The action requires a Project ID to specify which project's task lists to retrieve. Optional Filter By and Order By parameters allow for refined queries.

Use cases: Generate project structure reports, sync task list configurations to project templates, or build dashboards showing task list distributions.

This action retrieves all work types configured in your Awork account. Useful for populating dropdowns in other systems, generating reports on task categorization, or syncing work type configurations.

Key parameters: The action includes a Return All toggle, a Filter By field for applying criteria, and an Order By field for sorting results.

Use cases: Populate work type options in external forms or interfaces, audit and report on work type usage across projects, or sync work type configurations between environments.

This action updates the status of a specific project task. Essential for workflow automation where task statuses need to change based on external events, time-based triggers, or integration with other systems.

Key parameters: The action requires a Task ID to identify which task to update, and a Status ID to specify the new status to apply.

Use cases: Automatically mark tasks complete when related activities finish, update task statuses based on calendar events or deadlines, or sync task status changes from other project management tools.

This action adds a tag to a specific project task in Awork. Tags help categorize and filter tasks, and this action enables automated tagging based on task content, source, or other criteria.

Key parameters: The action requires a Task ID to identify which task to tag, and a Tag Name field to specify the tag to add.

Use cases: Automatically tag tasks based on their content or source, add priority tags when deadlines approach, or apply category tags based on integration triggers.

This action sets a custom field value for a project task. Custom fields extend Awork's data model, and this action enables automated population of these fields based on external data or workflow logic.

Key parameters: The action requires a Task ID to identify which task to update, and a Custom Field Definition ID to specify which custom field to set.

Use cases: Populate custom fields with data from CRM or ERP systems, set calculated field values based on workflow logic, or sync custom field data from external databases.

This action retrieves all tasks associated with a specific project, with filtering and sorting options. Essential for project reporting, task syncing, or building project dashboards.

Key parameters: The action requires a Project ID to specify which project's tasks to retrieve. Optional Filter By and Order By parameters enable refined queries.

Use cases: Generate project progress reports, sync tasks to external reporting dashboards, or identify overdue or at-risk tasks for escalation.

This action creates a new task within a project. One of the most commonly used actions for automating task creation based on external triggers, form submissions, or workflow conditions.

Key parameters: The required parameter is Project ID to specify where the task will be created. Optional parameters include Task Description, Type of Work ID for categorization, Task Status ID for initial status, Due Date for completion timing, and Planned Duration for time estimation.

Use cases: Create tasks automatically when support tickets are submitted, generate project tasks from form submissions, or create follow-up tasks when meetings are scheduled.

This action retrieves detailed information about a specific task using its unique identifier. Useful when you need to access task details for processing, reporting, or conditional workflow logic.

Key parameters: This action requires your Awork credentials and a Task ID field to specify which task to retrieve.

Use cases: Fetch task details for notification messages, retrieve task information for conditional workflow branching, or access task data for reporting or analytics.

This action retrieves all comments associated with a specific project. Useful for aggregating project discussions, creating comment reports, or syncing project communications to other platforms.

Key parameters: The action requires your Awork credentials, with the Resource parameter set to 'Project' and Operation set to 'Get Comments'.

Use cases: Archive all project discussions when projects close, generate project communication reports, or sync project comments to documentation systems.

This action creates a new task status within a specified project. Useful for dynamically establishing workflow stages or syncing status configurations from templates.

Key parameters: The action requires a Project ID to identify where the status will be created, and a Status Name for the new status. An optional Status Type parameter allows for further categorization.

Use cases: Set up project statuses from standardized templates, create custom workflow stages for specific project types, or sync status configurations across multiple projects.

This action creates a new task list under a specified project. Task lists help organize tasks into logical groups, and this action enables automated list creation based on project setup or template requirements.

Key parameters: The action requires a Project ID to identify where the task list will be created, and a Name for the task list.

Use cases: Automatically create standard task lists when new projects start, generate phase-based task lists from project templates, or create task lists based on team or department structure.

This action updates the status of a project. Essential for project lifecycle management, enabling automated status transitions based on milestones, dates, or external triggers.

Key parameters: The action requires a Project ID to identify which project to update, and a Project Status ID to specify the new status to apply.

Use cases: Automatically advance project status when milestones complete, update project status based on deadline triggers, or sync project status changes from portfolio management tools.

This action retrieves task lists associated with a specific project. Useful for understanding project organization or building project structure reports.

Key parameters: The action requires your Awork credentials and a Project ID to specify which project's task lists to retrieve.

Use cases: Generate project structure documentation, audit task list configurations across projects, or build project overview dashboards.

This action creates a new project in Awork. One of the most powerful actions for automating project setup, enabling instant project creation from CRM deals, form submissions, or calendar events.

Key parameters: The required parameter is Project Name. Optional parameters include Start Date for when the project begins, Due Date for completion timing, Project Type ID for categorization, Project Status ID for initial status, and Project Template ID to apply predefined templates.

Use cases: Automatically create projects when deals close in your CRM, generate projects from client onboarding forms, or set up projects based on contract signatures.

This action retrieves all task statuses configured for a specific project. Useful for understanding available workflow states or syncing status configurations.

Key parameters: The action requires a Project ID to specify which project's task statuses to retrieve. Optional Filter By and Order By parameters enable refined queries.

Use cases: Populate status dropdowns in external interfaces, audit status configurations across projects, or sync status options to reporting systems.

This action creates a new project status. Useful for establishing custom workflow stages for project lifecycles.

Key parameters: The action requires a Project ID to identify where the status will be created, and a Status Name for the new status. An optional Status Type parameter allows for categorization.

Use cases: Set up custom project lifecycle stages, create industry-specific project statuses, or sync project status configurations from templates.

This action retrieves detailed information about a specific project using its unique identifier. Essential when you need project data for reporting, conditional logic, or integrations with other systems.

Key parameters: This action requires your Awork credentials and a Project ID field to specify which project to retrieve.

Use cases: Fetch project details for notification messages, retrieve project information for conditional workflows, or access project data for reporting dashboards.

This action retrieves all project statuses across your Awork account with filtering and sorting options. Useful for portfolio-level reporting or understanding status distributions.

Key parameters: The action includes a Return All toggle, a Filter By field for applying conditions, and an Order By field for sorting results.

Use cases: Generate portfolio status reports, audit project status configurations, or build executive dashboards showing project distributions.

This action retrieves all projects from your Awork account with comprehensive filtering and sorting capabilities. Essential for portfolio management, reporting, and project discovery workflows.

Key parameters: The action includes a Return All toggle, a Filter By field for applying project criteria, and an Order By field for sorting projects by specified fields.

Use cases: Generate project portfolio reports, sync project lists to external dashboards, or identify projects meeting specific criteria for action.

This action permanently deletes a document from Awork. Use with caution—this action is useful for cleanup workflows, automated archiving processes, or maintaining document hygiene.

Key parameters: This action requires your Awork credentials and a Document ID field to specify which document to delete.

Use cases: Clean up temporary documents after processing, remove outdated documentation based on retention policies, or delete draft documents that were never finalized.