Actions82
- Client Actions
- Invoice Actions
- Payment Actions
- Receipt Actions
- Service Actions
- Team Actions
- User Actions
- Webhook Actions
- Descarga Masiva (SAT) Actions
Client → Get Customer Portal
AI-generatedOverview
This node operation interacts with the Gigstack API to retrieve a customer portal link or information for a specific client. It supports identifying the client either by their Client ID or by their email address. This operation is useful in scenarios where you need to programmatically access or share the customer portal associated with a client, such as in automated workflows for client management or support.
Use Case Examples
- Automatically fetch the customer portal link for a client after they are created in the system.
- Retrieve the customer portal for a client identified by email to send them a direct access link via email.
Properties
| Name | Meaning |
|---|---|
| Client ID or Email | The ID or email of the client used to identify the client for whom the customer portal is retrieved. |
| Identifier Type | Specifies whether the client is identified by their Client ID or by their email address. |
| Team ID | Optional Team ID for multi-team access in Gigstack Connect. Leave empty to use the default team. |
Output
JSON
id- The unique identifier of the client or customer portal response.email- The email address of the client if identified by email.url- The URL or link to the customer's portal retrieved from the Gigstack API.
Dependencies
- Gigstack API with an API key credential for authentication
Troubleshooting
- Ensure the client identifier (ID or email) is correct and exists in the Gigstack system to avoid 'client not found' errors.
- Verify that the API credentials are valid and have the necessary permissions to access client data.
- If using Team ID, confirm that the team exists and the API key has access to it.
- Handle API rate limits or network issues that might cause request failures.