Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
The "Get Cards Jump" operation in the "Cards" resource retrieves specific card information from an external integration by querying with identifiers related to that integration. This node is useful when you want to fetch detailed card data linked to various third-party services or platforms integrated into your workflow.
Typical use cases include:
- Fetching card details from a project management tool or CRM system integrated via an API.
- Retrieving card metadata for display, processing, or further automation steps.
- Using identifiers like integration type and slug to dynamically access cards across multiple external systems.
Properties
Name | Meaning |
---|---|
Integration Type | Type of card to retrieve. Users should contact support for a list of valid types per integration. |
Integration Slug | Identifier string representing the external integration from which to get the card. |
Additional Query Parameters | Optional parameters to refine the query: • Integration Id: ID of the entity in the external system. • Integration Identifier: Alternative identifier if Integration Id is not set. |
Output
The node outputs JSON data containing the card information retrieved from the external integration based on the provided query parameters. The exact structure depends on the external service's response but generally includes card attributes such as IDs, names, statuses, or other metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the external service.
- Needs configuration of the base URL for the API endpoint in the node credentials.
- Depends on the external integration's API supporting query parameters like
integration_type
,integration_slug
, and optionallyintegration_id
orintegration_identifier
.
Troubleshooting
- Missing or incorrect integration type/slug: The node may fail to retrieve data if these required fields are incorrect or unsupported. Verify values with the external service documentation or support.
- Invalid or missing API credentials: Authentication errors will occur if the API key or base URL is misconfigured.
- Ambiguous identifiers: If both
integration_id
andintegration_identifier
are missing or invalid, the query might return no results or errors. - Network or API errors: Timeouts or server errors from the external API can cause failures; check connectivity and API status.
Links and References
- Contact [email protected] for detailed lists of supported integration types.
- Refer to the external integration’s API documentation for specifics on query parameters and response formats.