Actions90
- Activity Actions
- Company Actions
- Contact Actions
- Deal Actions
- Project Actions
- User Actions
Overview
This node interacts with the MOCO API to perform operations related to activities. Specifically, the 'Get' operation under the 'Activity' resource retrieves detailed information about a specific activity by its ID. This is useful for scenarios where you need to fetch and use activity data within an automation workflow, such as tracking time entries or reviewing logged work details.
Use Case Examples
- Retrieve details of a specific activity by providing its Activity ID to integrate with project management or time tracking systems.
- Use the activity data to generate reports or trigger further actions based on the activity's attributes.
Properties
| Name | Meaning |
|---|---|
| Activity ID | The unique identifier of the activity to retrieve. This is a required string input. |
Output
JSON
id- The unique identifier of the retrieved activity.date- The date when the activity was logged.project_id- The ID of the project associated with the activity.task_id- The ID of the task associated with the activity.seconds- The duration of the activity in seconds.description- A textual description of the activity.billable- Indicates if the activity is billable.tag- Tags associated with the activity.remoteService- External service linked to the activity.remoteId- Identifier in the external service.remoteUrl- URL to the external service entry.
Dependencies
- MOCO API with authentication credentials
Troubleshooting
- Ensure the Activity ID provided is valid and exists in the MOCO system to avoid 'not found' errors.
- Check API credentials and permissions if the node fails to authenticate or access the activity data.
- Handle API rate limits or network issues that might cause request failures.
Links
- MOCO API Documentation - Activities - Official MOCO API documentation for activities, detailing endpoints and data structures.