Connectors
Adobe Workfront
Enabling Agentforce agents to interact with Adobe Workfront for project management, task tracking, time logging, and document handling.
The Adobe Workfront Connector for ACP allows Agentforce agents to integrate with your organization’s work management lifecycle, facilitating interactions with projects, tasks, users, documents, and issues within Workfront. This enables agents to automate workflows, retrieve project status, manage tasks, and assist users with their Workfront activities.
Purpose and Capabilities
This Connector provides tools to interact with Adobe Workfront’s API, covering common work management operations:
Tool Name | Description | Example Inputs |
---|---|---|
adobe_workfront_search_projects | Searches for projects based on name, status, or other criteria. | search_query , status_filter (optional) , fields_to_retrieve (optional) |
adobe_workfront_get_project_details | Retrieves detailed information for a specific project ID. | project_id , fields_to_retrieve (optional) |
adobe_workfront_create_project | Creates a new project in Workfront. | project_name , template_id (optional) , portfolio_id (optional) , project_data_map |
adobe_workfront_update_project | Updates details of an existing project. | project_id , update_data_map |
adobe_workfront_search_tasks | Searches for tasks within a project or across projects. | project_id (optional) , search_query , status_filter (optional) |
adobe_workfront_get_task_details | Retrieves detailed information for a specific task ID. | task_id , fields_to_retrieve (optional) |
adobe_workfront_create_task | Creates a new task, optionally linked to a project. | task_name , project_id (optional) , task_data_map |
adobe_workfront_update_task | Updates details of an existing task. | task_id , update_data_map |
adobe_workfront_log_time_on_task | Logs time spent on a specific task. | task_id , hours_spent , log_date , comment (optional) |
adobe_workfront_get_user_details | Retrieves information about a Workfront user. | user_id or username |
adobe_workfront_upload_document_to_project | Uploads a document to a specified project or task. | project_id or task_id , file_name , file_content_base64 , description (optional) |
adobe_workfront_get_document_details | Retrieves metadata or downloads a document. | document_id |
adobe_workfront_create_issue | Creates a new issue, optionally linked to a project or task. | issue_name , description , project_id (optional) , task_id (optional) |
adobe_workfront_get_issue_details | Retrieves details for a specific issue. | issue_id |
Prerequisites
- Adobe Workfront Instance: An active Adobe Workfront instance.
- API Key or OAuth 2.0 Client:
- API Key: A valid API key generated from a Workfront user profile with appropriate system-level access (e.g., System Administrator or a user with specific API access rights).
- OAuth 2.0 Application: Alternatively, an OAuth 2.0 application can be configured in Workfront for server-to-server or user-delegated authentication, providing a Client ID and Client Secret.
- User Permissions: The user associated with the API Key (or the user context for OAuth) must have the necessary permissions in Workfront to perform the actions invoked by the tools (e.g., create projects, update tasks, view documents). This includes access levels and sharing permissions on objects.
- Understanding of Workfront Concepts: Familiarity with Workfront terminology like Projects, Tasks, Issues, Portfolios, Programs, Users, Documents, Custom Forms, etc.
Setup Instructions
- Obtain API Key or Configure OAuth 2.0 Application:
- API Key:
- Log in to Workfront as a user with API access.
- Navigate to your user profile/settings area (often under “My Settings” or similar).
- Locate the API Key section and generate/copy the key.
- OAuth 2.0 Application (if preferred/required):
- As a Workfront administrator, navigate to Setup > System > OAuth2 Applications.
- Create a new application, configure the grant types (e.g., Client Credentials for server-to-server), and define scopes.
- Note the Client ID and Client Secret.
- API Key:
- Configure ACP Connector:
- The ACP administrator will configure the Adobe Workfront Connector settings within ACP.
- This will involve securely storing the API Key (or Client ID/Secret for OAuth), the Workfront instance URL (e.g.,
yourcompany.my.workfront.com
), and specifying the authentication method.
- Verify Connection:
- Use a simple tool like
adobe_workfront_search_projects
with a known project name oradobe_workfront_get_user_details
for the API user to test connectivity and authentication.
- Use a simple tool like
Common Use Cases
- Automated Project Creation: Agent creates a new Workfront project based on an approved sales order or service request from another system.
- Task Management & Assignment: Agent creates tasks under a project, assigns them to users, or updates task statuses based on external triggers.
- Status Reporting: Agent retrieves project status, task completion percentages, or issue summaries to provide updates.
- Time Logging Automation: Agent logs time against tasks based on calendar events or other activity trackers.
- Document Synchronization: Agent uploads final deliverables or important documents to relevant Workfront projects.
- Issue Tracking: Agent creates issues in Workfront when problems are reported in connected systems.
Troubleshooting Tips
- Authentication Errors (401 Unauthorized):
- Verify the API Key is correct and has not expired or been revoked.
- For OAuth, ensure the Client ID/Secret are correct and the token generation process is successful.
- Check that the Workfront user associated with the API key/OAuth app is active and has login rights.
- Permission Denied (403 Forbidden):
- The Workfront user lacks the necessary access level or sharing permissions for the object (project, task, etc.) or action being attempted. Review user permissions in Workfront.
- Object Not Found (404 Not Found):
- Double-check IDs for projects, tasks, users, etc. Workfront IDs are case-sensitive.
- Ensure the object exists and has not been deleted.
- Invalid Request/Data:
- Ensure required fields are provided for creation/update operations.
- Check data formats (e.g., dates, custom field values) against Workfront’s expectations.
- Verify API endpoint paths if direct API calls are being constructed.
- API Rate Limits: Workfront APIs have rate limits. If making many calls, implement appropriate error handling and retry logic with backoff.
- Custom Forms & Fields: If interacting with custom forms or fields, ensure the API names for these fields are used correctly and the data provided matches the field type.
This connector facilitates seamless integration between Agentforce agents and Adobe Workfront’s robust work management capabilities.