Actions12
Overview
The Accelo Activity: Get operation node retrieves activity records from the Accelo platform, allowing users to filter and fetch specific activities based on various criteria. This node is useful for automating workflows that require access to activity logs, such as tracking communications, monitoring project updates, or integrating activity data with other systems.
Practical examples:
- Fetching all activities related to a particular contact or company.
- Retrieving activities assigned to a specific staff member.
- Filtering activities by their unique identifiers for reporting or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of filters to narrow down the activities returned. Options include: |
| - Activity ID: Filter by the unique identifier of the activity. | |
| - Parent ID: Filter by the parent entity's identifier (e.g., related object). | |
| - Staff: Filter activities assigned to a specific staff member. |
Output
The output is a JSON array where each item represents an activity record retrieved from Accelo. Each activity object typically contains fields such as:
id: The unique identifier of the activity.parent_id: The identifier of the parent entity associated with the activity.staff: The staff member associated with the activity.- Additional fields may be present depending on the Accelo API response.
Note: The exact structure of each activity object depends on the Accelo API and may include more details relevant to the activity.
Dependencies
- External Service: Requires access to the Accelo API.
- Credentials: An n8n credential named
acceloApimust be configured with valid API credentials. - Environment: No special environment variables are required beyond standard n8n setup.
Troubleshooting
Common Issues:
- Invalid Credentials: If the provided API credentials are incorrect or expired, authentication errors will occur.
- Missing Required Filters: If no filters are set, the node may return a large dataset or none, depending on the API defaults.
- API Rate Limits: Excessive requests may trigger rate limiting by Accelo.
Error Messages:
"401 Unauthorized": Check your Accelo API credentials in n8n."400 Bad Request": Ensure that filter values (such as IDs) are valid numbers and correspond to existing records."Network Error": Verify network connectivity and Accelo API availability.