Custom trigger app calling itself

monday Apps & Developers
, , , ,
1

Hi guys,

I’m developing an app which gets data from external API and returns them into a board. The app works perfectly fine if I use build-in trigger (“When column changes”). However, I’m forced to use custom trigger (“When text or number column changes”) to restrict trigger column type. To achieve that, app uses custom trigger in which specifies trigger column type to text, long text or number only.

Screenshot 2024-09-23 at 15.18.51
Screenshot 2024-09-23 at 15.18.51679×902 32.7 KB

I implemented subscription/unsubscription endpoints to get the webhookUrl and manage the subscription. I’m able to call the webhookUrl with in Postman using tunnel to my localhost. The action is called properly as expected.

Now, I’m stuck with calling it programmatically. I thought, I’d create a new webhook which should call the webhookUrl via my app:

  1. When column changes
  2. Call my monday app endpoint (using monday code)
  3. Select proper webhookUrl from app storage
  4. Call selected webhookUrl
  5. Action trigger is called and make the integration running

Questions:

  1. Does it make sense to you?
  2. Is there any simpler way to how to make it?
  3. If not, how to create a webhook pointing to your app? I use hostname from subscribe request however it looks kind of dummy.

Thank you in advance!

2

Here is how I think it could work.

Screenshot 2024-09-24 at 14.43.33
Screenshot 2024-09-24 at 14.43.33644×1002 63.9 KB

3

Hello there @MichalJurnik,

Would you be able to please fill this form adding as much information as possible to it so that our team can take a look into it?

1 Like
4

Thank you, @Matias.Monday! I submitted the form with a question regarding whether this is the best approach.

I managed to create a board webhook that triggers my app’s endpoint, which then calls the webhook URL. However, it feels like a roundabout way of doing things. I’d appreciate any suggestions for a more direct solution!

5

Hi @MichalJurnik,

I took a look into your email and I believe your flow looks good!

But if you have more questions, please feel free to reply in the email thread we have :smile:

1 Like
6

Thank you @Matias.Monday one more time. I was able to develop a solution based on my idea and your help.

The magic trick is that you need to create an integration of your app (manually) to call your subscribe endpoint (app) which creates webhook (automatically) calling your trigger. Once the trigger is called, you need to identify the webhook and call proper webhookUrl :smile:

Step by step solution:

  1. custom trigger calls my app’s subscribe endpoint. There are subscriptionId and webhookUrl in call’s payload
  2. the app creates a new webhook via API. The webhook url aims to app’s trigger-call endpoint and contains parameter subscriptionId in url. Example: https://here.should.be.your.domain/trigger-call?subscriptionId=123. Note: there needs to be implemented two endpoints for route trigger-call. The first without authorization returning challenge and the second maintain your workflow.
  3. the app stores subscriptionId and webhookUrl in app’s local storage
  4. once the webhook trigger is performed, the trigger-call endpoint is called. Here the app extracts the subscriptionId parameter from url. Based on subscriptionId gets webhookUrl from app’s local storage and call webhookUrl generated from the step 1. Obviously, the call needs to be authorized in header and contains parameters in body based on your custom trigger output parameters.

The final outcome looks like:

Screenshot 2024-10-02 at 10.00.34
Screenshot 2024-10-02 at 10.00.341632×393 38.6 KB

7

Thank you for sharing this @MichalJurnik !!