We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've setup a webhook to ping an n8n instance whenever a URL is hoarded. It works fine but I was surprised to see two calls for each new URL hoarded.
I checked the payload and looks like I get one for "operation": "created" and a second one for "operation": "crawled"
"operation": "created"
"operation": "crawled"
I double-checked and only created is selected as event. Just for fun I set it up to only send events on crawled but I still get two calls.
created
crawled
I would like to only get created or crawled depending on what I select.
Just to be greedy I would love a new Event type - AI tagged - which includes the assigned tags.
Thanks for the awesome app !
No response
0.22.0
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the Bug
I've setup a webhook to ping an n8n instance whenever a URL is hoarded. It works fine but I was surprised to see two calls for each new URL hoarded.
I checked the payload and looks like I get one for
"operation": "created"
and a second one for"operation": "crawled"
I double-checked and only
created
is selected as event. Just for fun I set it up to only send events oncrawled
but I still get two calls.Steps to Reproduce
Expected Behaviour
I would like to only get created or crawled depending on what I select.
Just to be greedy I would love a new Event type - AI tagged - which includes the assigned tags.
Screenshots or Additional Context
Thanks for the awesome app !
Device Details
No response
Exact Hoarder Version
0.22.0
Have you checked the troubleshooting guide?
The text was updated successfully, but these errors were encountered: