Webhook support - create AtomicData by calling a webhook
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are named. Start by reviewing the webhook requirements in this issue, then identify the server entry point for POST requests and resource creation; done means a target-scoped webhook accepts JSON, enforces the creator's rights, and creates the resource.
Written by the indexing model from the issue text.
Description
Create instances of resources in one specific scope (parent) without needing an Agent / Commits / Token or whatsoever. Just send a POST request with a JSON body to that webhook and you're done!
When is this useful
- Linking to other services / integrating with other tools (through hubs like IFTTT). For example: create a person every time a form has been submitted on airtable.
How to build this: ClassExtender plugin
- We create a new
WebHookclass + ClassExtender (plugin) - They have a certain
targetwhere they write the information - They have a
POSThandler that parses the incoming JSON and creates a new resource in the hierarchy, at thetargetlocation. - The rights of the Agent who created the
WebHookare checked when creating a new resource through that webhook.
Not to be confused with
The other direction in which webhooks can work: as notifications when something in AtomicServer changes #77. This is also very valuable, but for a different usecase.
- Dominant language
- TypeScript
- Stars
- 1.6k
- Forks
- 82
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 205
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ontola/atomic-server
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ontola/atomic-server#1569 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ontola/atomic-server#1494 ·
-
browser
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
ontola/atomic-server#1213 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ontola/atomic-server#1588 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ontola/atomic-server#1584 · 1 comment ·
All issues in ontola/atomic-server
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·