Skip to content
New issue

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

Contest Bot: Implement Webhook #10375

Open
rbennettcw opened this issue Dec 18, 2024 · 1 comment · May be fixed by #10529
Open

Contest Bot: Implement Webhook #10375

rbennettcw opened this issue Dec 18, 2024 · 1 comment · May be fixed by #10529
Assignees

Comments

@rbennettcw
Copy link
Contributor

rbennettcw commented Dec 18, 2024

Currently, there is a Farcaster contest bot already implemented, which programmatically sends messages to users via Neynar API: #10335

We need to setup the CW app to listen to Farcaster mentions (e.g. @contestbot) so that the bot can respond to those messages.

Relevant docs: https://docs.neynar.com/docs/listen-for-bot-mentions

Required artifacts:

  • Config: Neynar webhook setup (in Neynar dev dashboard) for QA + production
  • Route: Add a new webhook route in integration router which emits ContestBotMentioned event w/ Cast payload (using signature validation middleware)
  • Policy: Add a new policy (or use existing FarcasterWorkerPolicy) to handle the ContestBotMentioned event (the handler is empty for now, will implement in another ticket)

Acceptance Criteria

  • CW app should listen for contest bot mentions

Other Considerations

  • There's separation of local, QA and production environments for the Neynar/bot configs. The bot for each environment should have a different Farcaster handle.
@rbennettcw rbennettcw self-assigned this Dec 18, 2024
@rbennettcw rbennettcw changed the title Contest Bot: Setup bot mention listener Contest Bot: Webhook Dec 18, 2024
@rbennettcw rbennettcw changed the title Contest Bot: Webhook Contest Bot: Implement Webhook Dec 18, 2024
@dillchen
Copy link
Contributor

dillchen commented Jan 4, 2025

Unassigned @Rotorsoft as @rbennettcw shoumd be back Monday, and moving it to teed up / in prog

@rbennettcw rbennettcw linked a pull request Jan 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants