Financial Cents

Interact with the Financial Cents API

Actions21

Overview

This node interacts with the Financial Cents API to list projects. It fetches a paginated list of projects from the API, supporting both the default /work path and an alternative /projects path depending on the API version or configuration.

Common scenarios where this node is beneficial include:

  • Retrieving all projects for reporting or synchronization purposes.
  • Fetching a subset of projects with pagination controls for display in dashboards or further processing.
  • Integrating project data into workflows that require up-to-date project lists from Financial Cents.

Practical example:

  • A user wants to automate weekly reporting by fetching all active projects from Financial Cents and then sending summaries via email.
  • Another use case is syncing project data into a CRM or project management tool by periodically listing projects and updating external systems.

Properties

Name Meaning
Debug: Include Raw Response If enabled, each output item will include the raw JSON response from the API under __raw.
Use /projects path (not /work) Selects whether to use the /projects API endpoint instead of the default /work endpoint.
Page The page number of results to fetch (minimum 1).
Per Page Number of projects to return per page (between 1 and 200).
Return All If true, automatically paginate through all pages until all projects are retrieved.
Limit When Return All is enabled, limits the total number of projects returned (0 means no limit).

Output

The node outputs an array of JSON objects representing individual projects. Each object contains the project data fields as returned by the Financial Cents API.

If "Debug: Include Raw Response" is enabled, each item also includes a __raw field containing the full raw API response for that request, useful for debugging or advanced processing.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Financial Cents API.
  • The node uses HTTP requests to the Financial Cents API endpoints (/work or /projects).
  • No additional environment variables or configurations are required beyond the API credential.

Troubleshooting

  • Common issues:

    • Incorrect API credentials will cause authentication failures.
    • Using the wrong API path (/work vs /projects) may result in empty responses or errors if the API version differs.
    • Pagination parameters out of range (e.g., perPage > 200) may cause API errors.
  • Error messages:

    • Authentication errors typically indicate invalid or missing API keys; verify credentials.
    • "User ID is required" or similar errors do not apply here but appear in other operations.
    • If no projects are returned, check if the correct API path is selected and that projects exist in the account.
  • Resolution tips:

    • Enable "Debug: Include Raw Response" to inspect the exact API response.
    • Adjust pagination settings to valid ranges.
    • Confirm API endpoint path matches your Financial Cents instance.

Links and References

Discussion