Flowtly

Interact with Flowtly API
Join our community

Actions2

Overview

This node integrates with the Flowtly API to manage organizations and authentication. Specifically, for the Organization - Get All operation, it retrieves a paginated list of organizations from the Flowtly platform.

Typical use cases include:

  • Fetching all organizations accessible by the user for reporting or synchronization.
  • Automating workflows that require organization data from Flowtly.
  • Integrating organization data into other systems or dashboards.

For example, you might use this node to pull all organizations page by page, then process or store them in your CRM or database.

Properties

Name Meaning
Page Page number to retrieve (pagination)
Items Per Page Number of organizations per page

These properties control pagination when fetching organizations.

Output

The node outputs an array of organization objects under the json field. The structure corresponds to the Flowtly API response's "hydra:member" property, which contains the list of organizations.

Example output snippet:

[
  {
    "id": "org_123",
    "name": "Example Organization",
    "createdAt": "2023-01-01T00:00:00Z",
    ...
  },
  ...
]

If the API response does not contain "hydra:member", the entire response JSON is returned as-is.

No binary data is output by this operation.

Dependencies

  • Requires an API authentication token (JWT) from Flowtly.
  • The node expects either:
    • A valid token passed in the input item's json.token field, or
    • An API key credential configured in n8n for Flowtly.
  • The base URL used is https://app.flowtly.com/api.
  • The node uses HTTP GET requests with Bearer token authorization.

Troubleshooting

  • No token found error:
    Occurs if no token is provided via input or credentials.
    Resolution: Perform a login operation first to obtain a token, or configure the API key credential properly.

  • Failed to get organizations:
    Could be due to network issues, invalid token, or API errors.
    Resolution: Check the token validity, network connectivity, and ensure the Flowtly API is reachable.

  • Login failed / No token received:
    When performing login, if the response does not contain a token, the node throws an error.
    Resolution: Verify username and password correctness and API availability.

  • Parsing errors:
    If the login response cannot be parsed as JSON, it indicates unexpected API response format.
    Resolution: Confirm API stability and correct endpoint usage.

Links and References

Discussion