Webhook Workflow Trigger

[showcal_rob]

It would be AMAZING if you could trigger a workflow via a webhook. Primary use case for this would be to send notifications, from external services like Make.com The reason is because I have action buttons that notify when I’m making an external API call, but I have no way to notifying them when the external API call is finished.

Alt option is to have a “wait for trigger/response” step, which waits until the external API call returns some information, and then continues with the workflow.

This would be extremely helpful, to accommodate for the lack of “realtime” syncing between Airtable and Noloco.

[thecasemaster]

PLEASE give us this trigger. I need a way to send notifications to users when changes outside of noloco happen and the limitations on the ways a workflow can be triggered seem to be a major gap in capabilities. One of the big things I was so excited about when I started working with noloco was the ability to have the notifications system but it needs some work to really be as powerful and functional as I need it to be.

[buildwithjoel]

This is huge. Being able to have a Noloco webhook pick data up would be SO helpful.

[Brandi_Bullock]

There’s workarounds using GraphQL, but would be a benefit for sure!

[Brandi_Bullock]

As a workaround, you can add comments to records via GraphQL and it will notify users

[lukebranford]

I did something similar, but because I didn’t want the comments on records, I built a simple notifications table in Noloco, then send a record via API which triggers workflow with notification send. Works really well!

[seanvosler]

EDIT: I didnt realize i already posted this months ago, sorry lol… this is an easier to read version anyways:

I do this in make via the following mechanism (it’s convoluted but works like a charm hah)…

Step 1 - Find the workflow ID via chrome developer tools.

How to Find Workflow ID:

1. go to the workflow editor and navigate to the workflow editor

2. Open Chrome Developer Tools go to the ‘Network Tab’ and click the “Fetch/XHR” button

3. get ready to run your workflow via the ‘test’ functionality (top right within noloco

4. before you trigger your test clear the network logs
   

5. Run the workflow via ‘test workflow’ in noloco and inspect chrome console ‘Network Tab’ to find the POST request which contains the workflow ID and other information.
   Note, the ID is not the same as the ID you might see in the admin workflow URL area. You need the one that’s posted to the server when it’s run.

You will find it under the ‘payload’ tab of one of the API requests…

Example 1:

Example 2:

Often the proper POST request is following the duel “T” API requests… It is always within a request to api.portals.noloco.io/data, there are a lot of them, i usually just click on payload and cycle through them…

Once you have the workflow ID from the FETCH Request you can set things up in Make:

Copy this and add your values:

Response: {"data": {"runWorkflow": "12345" }}
Query: "mutation runWorkflow($workflowId: String!, $recordId: ID!) i\n runWorkflow(workflowId: $workflowId, recordId: $recordId) \n}" {workflowId: "fvXXXB5", recordId: "4945"}

Important! The recordId: "{record_id_number}" is the ID of the record in noloco you want the workflow to execute with, it is the input record. Since workflows are set to specific datatypes you don’t need to include anything but the record ID.

Example mutation to use in the MAKE+Noloco custom API call:

mutation RunWorkflow {
  runWorkflow(recordId: "id-of-record-used-in-workflow", workflowId: "ADD-HERE")
}

SUPER EASY

lol

[darragh]

Thanks @seanvosler and everyone else for your input here!

More workflows triggers are definitely something we’re looking into.

In the meantime, one of the easiest ways to do this is to add a field like a date field to your table such as ‘workflow last triggered at’ and then create your workflow to only watch changes to this field.

Then, when you want to trigger the workflow, you use our existing modules in Make/Zapier to update this field with the current time.

This would achieve the exact same thing, without having to worry about webhooks or GraphQL.