Actions18
Overview
This node integrates with the Linear API to perform advanced operations on various Linear resources, including members. Specifically, for the Member resource with the Get Many operation, it retrieves multiple member records from a Linear workspace.
Typical use cases include:
- Fetching a list of all members in a Linear workspace or team.
- Retrieving a limited subset of members for reporting or processing.
- Automating workflows that require user/member data from Linear.
For example, you might use this node to get all members to send them notifications or to sync member data with another system.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all member results or only up to a given limit. |
| Limit | The maximum number of member results to return if "Return All" is set to false (1 to 100). |
Output
The node outputs an array of JSON objects, each representing a member retrieved from Linear. Each member object contains details such as member ID, display name, email, and other metadata provided by the Linear API.
No binary data output is produced by this operation.
Example output item structure (simplified):
{
"id": "member_id",
"displayName": "Member Name",
"email": "member@example.com",
// ... other member properties
}
Dependencies
- Requires an active connection to the Linear API via an API key credential.
- The node uses the official Linear SDK client internally to communicate with the Linear API.
- Proper API credentials must be configured in n8n for authentication.
Troubleshooting
Common issues:
- Missing or invalid API key credential will cause authentication failures.
- Requesting too many members without setting "Return All" may result in truncated results.
- Network connectivity issues can prevent successful API calls.
Error messages:
"Member ID is required for getting a member."— occurs if trying to get a single member without specifying the member ID."The operation 'getMany' is not supported for resource 'member' via JSON parameters."— indicates unsupported operation or malformed JSON input.- General API errors from Linear will be surfaced; ensure API limits and permissions are respected.
Resolutions:
- Verify API key validity and permissions.
- Use "Return All" carefully to avoid large data loads.
- Check network connectivity and retry failed requests.