Flow event and action
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 2.2k
- Forks
- 587
- Avg merge
- 18h 27m
- Merged PRs (30d)
- 333
Description
We would like to equip Talk for Nc 18 with following events and actions:
Events
- call has finished (provide conversation name, start and end date, participants, conversation message in this time frame)
Actions (Operations)
- write a message into a Talk conversation
- create a Talk notification (so probably like ^ but one on one)
The actions should be independent of the triggering event, nevertheless should support/consider some context (e.g. the event itself like file modified, file path/name for Files, or also tag when in combination with a tagging event).
An Action (Operation in tech terms) implementation to look at could be https://github.com/nextcloud/workflow_script/pull/22
As discussed @danxuliu :) Don't hesitate to reach out for any questions, starter points, API stuff, also missing bits.
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.
Research direction
Start by reviewing the workflow_script pull request linked in the issue and the existing Talk workflow integration. Confirm which listed event and action items remain, including the context each operation must receive. Done means the requested Talk event and notification action are supported independently of their triggering event, with the stated conversation details and context available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100