Gigstack icon

Gigstack

Interact with Gigstack API for Mexican tax-compliant invoicing and payments

Client → Get

AI-generated

Overview

This node interacts with the Gigstack API to retrieve detailed information about a specific client using their Client ID. It is useful in scenarios where you need to fetch client data for invoicing, payments, or customer management within the Gigstack platform. For example, you can use this node to get client details before creating an invoice or validating client information.

Use Case Examples

  1. Retrieve client details by providing the Client ID to integrate client data into your workflow.
  2. Fetch client information to validate or update client records in your system.

Properties

Name Meaning
Client ID The ID of the client to retrieve information for.
Team ID Optional Team ID for multi-team access in Gigstack Connect. Leave empty to use the default team.

Output

JSON

  • id - Unique identifier of the client.
  • email - Email address of the client.
  • name - Name of the client.
  • company - Company name associated with the client.
  • phone - Phone number of the client.
  • legal_name - Legal name of the client.
  • tax_id - Tax identification number of the client.
  • tax_system - Tax system applicable to the client.
  • use - Usage information related to the client.
  • bcc - Blind carbon copy email addresses associated with the client.
  • address
    • street - Street address of the client.
    • exterior - Exterior number of the client's address.
    • interior - Interior number of the client's address.
    • neighborhood - Neighborhood of the client's address.
    • city - City of the client's address.
    • state - State of the client's address.
    • zip - ZIP code of the client's address.
    • country - Country of the client's address.
    • municipality - Municipality of the client's address.
  • metadata - Additional metadata associated with the client.

Dependencies

  • Gigstack API key credential

Troubleshooting

  • Ensure the Client ID provided is correct and exists in the Gigstack system to avoid 'client not found' errors.
  • Verify that the API key credential for Gigstack is valid and has the necessary permissions to access client data.
  • If using Team ID, confirm that the team exists and the API key has access to it to prevent authorization errors.
  • Handle API rate limits or network issues that might cause request failures by implementing retry logic or error handling in the workflow.

Links

Discussion