Webhook-question

In your dev.documentation you state that changes in custom fields doesn't trigger webbhook. Not Yet. 

When will it be supported?? This is a total showstopper for us. 

 

We use the api to sync between wrike and our invoicing system. 

Scenario

Task is created

Webhook triggers

Custom fields are edited to set the parameters for the invoicing system. 

Webbhook does'nt trigger, no sync occurs. ERROR 

 

You don't have to say anything about the data. Just that the task is updated

{
   "taskId""IEAADQQLKQAKOFAB",
   "webhookId""IEAADQQLJAAAAULN",
   "eventAuthorId""KUAALDRX",
   "eventType""TaskCustomFieldsChanged",
   "lastUpdatedDate""2016-11-22T11:09:58Z"
}

 

The endpoint will query wrike about the task. 

 

PLEASE FIX THIS :)

Kind regards

// Johan

3
7 Kommentare
Spot On Innovative Approach Stellar Advice
Avatar

Hi Johan! Understand your concerns, this functionality  could be really useful! I am afraid at the moment we have no concrete plans on the feature, however our Product team has included it into the backlog for future improvements. 

Pavel M Community Team at Wrike Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen

0
Aktionen für Kommentare Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi,

I would be very interested by this feature too !

Anyway, I'm currently setting up some webhooks and I have a question concerning some restrictions I want to apply.

I created a working endpoint, I'm receiving payloads, everything's fine.

I just want to make sure only Wrike will post anything to my endpoint. The token does not seem to be included in the payloads.

So I want to restrict the access to the endpoint using the IP address. Logs show that it's always the same IP posting the payloads. Is this IP subject to changes or can I rely on it ? (I will add some other layers of security but it's a start).

Do you have some insights to share on how to secure the endpoint ?

Thanks a lot,

1
Aktionen für Kommentare Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Hi Yannick! Accepting payloads from wrike.com only could be a good idea - I think you would need to make sure to whitelist all IP's falling into the range of 160.19.162.0/24, this is Wrike's range of addresses for wrike.com 

Pavel M Community Team at Wrike Erfahren Sie mehr über Wrikes leistungsstarke Funktionen und lernen Sie Anwendungsbeispiele kennen

0
Aktionen für Kommentare Permalink
Spot On Innovative Approach Stellar Advice
Avatar

+1 for Custom Field change triggering a webhook. While not a showstopper, this would be a very helpful feature for us.

2
Aktionen für Kommentare Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Agreed!

 

 

1
Aktionen für Kommentare Permalink
Spot On Innovative Approach Stellar Advice
Avatar

+1 for this request. It's also a showstopper for us as well. You at least want to be informed that "a" field has changed. Ideally it also passes the field name, old value and new value in the payload.

1
Aktionen für Kommentare Permalink
Spot On Innovative Approach Stellar Advice
Avatar

Wohoo... All webh****ers

 

Now changes in  custom fields is supported...

 

https://help.wrike.com/hc/en-us/community/posts/360022765474--From-Wrike-Webhooks-are-live

https://developers.wrike.com/documentation/api/webhooks/event-types

 

TaskCustomFieldChanged Fired when a custom field value on a custom field is changed

 

0
Aktionen für Kommentare Permalink

Folllowing List for Post: Webhook-question
[this list is visible for admins and agents only]

Didn’t find what you were looking for? Write new post