Remove 'ignore updates' for a given extension in watchful.li

What this operation does

Remove 'ignore updates' for a given extension

• POSTChanges data · extensionswatchful.li/extensions/{id}/unignore

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which watchful.li operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other watchful.li operations

• Create a SSO UserPOST · changes data
• Create a tagPOST · changes data
• Create a sitePOST · changes data
• Create a feedbackPOST · changes data
• Delete a specific SSO UserDELETE · changes data
• Update a SSO UserPUT · changes data
• Create a custom log for a specific websitePOST · changes data
• Add tags for a specific websitePOST · changes data

All 59 watchful.li operations

Questions

Can HumDay remove 'ignore updates' for a given extension in watchful.li?

Yes. This operation is published in watchful.li's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my watchful.li data?

Yes — this is a POST operation, so it changes something in watchful.li. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your watchful.li account.

Where this came from

Read from a published API description for watchful.li at api.apis.guru/v2/specs/watchful.li/1.0.0/swagger.json. The description above is the provider’s own wording, not ours. Last published 2019-02-25.