Overview
The LoneScale Trigger node is designed to trigger an n8n workflow when a specific event occurs in a LoneScale workflow. It works by registering a webhook with the LoneScale API, so that when the selected LoneScale workflow emits an event, this node receives the data and starts the n8n workflow. This is particularly useful for automating processes based on events or changes within LoneScale, such as new data entries, status updates, or other workflow-specific triggers.
Practical examples:
- Automatically process leads when a LoneScale workflow completes.
- Start a notification sequence in n8n when a LoneScale task reaches a certain stage.
- Sync LoneScale workflow results into another system via n8n.
Properties
| Name | Type | Meaning |
|---|---|---|
| Workflow Name | options | Select one workflow from your LoneScale account. This is the workflow whose events will trigger this node. |
Output
The node outputs the body of the incoming HTTP POST request from LoneScale as JSON. The structure of this output depends on what LoneScale sends, but typically it will mirror the event payload from LoneScale.
Example output:
{
"workflowData": [
{
// ...fields sent by LoneScale in the webhook body
}
]
}
If LoneScale sends binary data, it will not be processed specially; only JSON payloads are handled.
Dependencies
- External Service: Requires access to the LoneScale API.
- API Key: You must provide valid LoneScale API credentials (API key) in the node's credentials section.
- n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common issues:
- Invalid API Key: If the LoneScale API key is missing or incorrect, workflows will not be listed, and webhooks cannot be registered.
- Webhook Registration Failure: If the webhook cannot be created (e.g., due to network issues or permission problems), the node will not trigger as expected.
- No Events Received: Ensure the correct LoneScale workflow is selected and that it is configured to emit events.
Error messages and resolutions:
"401 Unauthorized": Check your LoneScale API key in the credentials."404 Not Found"during webhook creation: Verify the selected workflow exists and is accessible."Webhook already exists": The node checks for existing webhooks and should handle duplicates, but if you see this error, try deleting old webhooks manually in LoneScale.