Start tasks from Latenode
A Latenode scenario can start a Jaah task with one HTTP request, and Jaah can tell a scenario when a task finishes. Both use features Jaah already has: a Webhook automation for requests coming in, and a webhook for events going out. To give agents Latenode's own tools instead, add a Latenode secret.
Who can do this: Owners and Admins of your organization. Only they see automations and webhooks.
Start a task from a scenario
- Make a Jaah API key with Create ticked on its Tasks row. See API keys. Tasks the scenario starts are filed as the key's owner.
- In Jaah, create an automation with Webhook as its event. On What, under
Target, pick Projects and the project, then describe the task. Quote what the scenario sends with placeholders, such as
{{body.title}}in Title and{{body.details}}in the description. - On the automation's Setup tab, under Endpoint, select Copy URL.
- In Latenode, add an HTTP Request node where the scenario should start the task. Set:
- Method:
POST; - URL: the address you copied;
- a header
Authorizationwith the valueBearerfollowed by the API key; - a header
Content-Typewith the valueapplication/json; - Body: JSON with the fields your placeholders name, such as
{"title": "…", "details": "…"}.
- Method:
- Run the node once in Latenode. On the automation's page in Jaah, the run shows the task it filed.
If no task appears, check the key: Jaah refuses a key that can't create tasks, and a revoked or expired one.
Tell a scenario when a task finishes
This needs a plan that includes webhooks.
- In Latenode, start a scenario with a Webhook trigger and copy its Production URL. The Development URL runs the scenario only once.
- In Jaah, create a webhook with that address as its URL. Under Events, tick what the scenario should react to, such as Task done and Task failed.
- Select Create, then copy the signing secret into the scenario if it checks signatures.
Each event reaches the scenario as JSON. The task's title, state and link are in data.task, and the event
type, such as task.done, is in type. See
What a delivery looks like.
Related
- Latenode: give agents Latenode's tools or a scenario's MCP tools.
- Create an automation: every event source and its settings.
- Fix a failing webhook: when Latenode stops receiving events.