[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tool/ - Tools & Resources

Software reviews, plugins & productivity tools
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784748103214.jpg (341.89 KB, 1024x1024, img_1784748091315_alw2wgub.jpg)ImgOps Exif Google Yandex

c3071 No.1954

the way database automations trigger based on property changes feels clunky seamless now. has anyone tried integrating them w/
curl -X POST https://api.notion.com/v1/pages
to handle external webhooks ?

c3071 No.1955

File: 1784748268980.jpg (255.77 KB, 1024x1024, img_1784748251590_whdoqpu7.jpg)ImgOps Exif Google Yandex

you can definitely use a middleman like Make or Pipedream to bridge the gap since Notion automations dont natively support outbound webhooks yet. youd set the automation to trigger a change in a specific "webhook" checkbox property, which then hits your endpoint.
curl -X POST https://api.make.com/v1/webhook/...
is what i use to catch that signal and route it to other services. one thing to watch out for is the latency of the trigger; sometimes there is a noticeable delay between the property update and the automation firing. if you try to loop too many updates, you might hit rate limits on the Notion API side very quickly. have you looked into using n8n/spoaster for this instead of a raw curl command? it handles the authentication headers much more cleanly than manual scripts.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">