Actions26
- Collections Actions
- Records Actions
- Fields Actions
- Chats Actions
- Files Actions
- User Contacts Actions
- Triggers Actions
Overview
This node interacts with the Cogfy Tables API to create a trigger associated with a specific field within a collection. The trigger is designed to receive request bodies on a designated JSON-type field, enabling automated workflows based on data changes or events in Cogfy Tables.
Common scenarios for this node include:
- Automating actions when new data is added or updated in a Cogfy Table.
- Integrating Cogfy Tables with other systems by triggering workflows upon data changes.
- Monitoring specific fields within collections to react dynamically to incoming data.
For example, you might use this node to create a webhook trigger that listens for updates on a particular JSON field in a collection, then processes or routes that data elsewhere automatically.
Properties
| Name | Meaning |
|---|---|
| Field Id | The ID of the JSON-type field that will receive the request body for the trigger. |
| Collection Id | The ID of the collection containing the specified field where the trigger will be created. |
Output
The node outputs JSON data representing the result of the trigger creation operation. This typically includes details about the newly created trigger such as its identifier, status, and configuration metadata. There is no indication that the node outputs binary data.
Dependencies
- Requires an active connection to the Cogfy Tables API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the Cogfy Tables API must be set in the node's credential configuration.
Troubleshooting
- Invalid Field or Collection IDs: If the provided
fieldIdorcollectionIddoes not exist or is incorrect, the API will likely return an error. Verify these IDs are correct and correspond to existing resources. - Field Type Mismatch: The
fieldIdmust refer to a JSON-type field. Using a field of another type may cause errors or unexpected behavior. - Authentication Errors: Ensure the API key or token is valid and has sufficient permissions to create triggers.
- Network Issues: Connectivity problems to the Cogfy Tables API endpoint can cause failures; verify network access and base URL correctness.
Links and References
- Cogfy Tables API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes