6d ago

Gossip: Trigger a webhook from an email

Gossip Multiple Emails Dispatch

TLDR

Create an email mapped to your webhook, the webhook will be called when an email will be received. It reacts instantly to emails. Check out the 1min demo in odysee

https://odysee.com/@jostiniane:a/gossip_dispatch:3

Long Story

I tried to share this previously in Reddit & HN but got 0 attention. I was hoping I could get some feedback here.

When I created this, I envisaged at least two use cases:

(main one for my workplace) Plug the generated email(s) into the monitoring system to create tickets in the project management software you are using when an alert is triggered
(for open source projects) Embed/Share the generated email with your users and have the email bug reports transformed into gitlab/gitea/github issues
(it could serve as a starting point for an open source business automation software)

This is in a very early stage, I am more than open to feature requests. I have have a bunch of improvements planned but would like to see if there's some interest first.

The project source is in gitea.v3m.net which is not public, I am open to creating a public mirror in your favorite public place (gitlab.com, github.com, ...).

I am also open to having the current instance serving right from your open source subdomain for those interested.

registration link: https://g.v3m.net/user/register (zero tracking just plain golang + htmx)

Opensource @programming.dev

cm0002 @lemmy.world

6d ago

Gossip: Trigger a webhook from an email

odysee.com /@jostiniane:a/gossip_dispatch:3

8 comments

I don't understand what you're doing here. I use your website to what?
Monitor my email and when I get one that matches the regex it'll make an API call?
Or is your website the API endpoint?
The video didn't help me understand.
- Thanks for having a look!
  Monitor my email and when I get one that matches the regex it’ll make an API call?
  It's this first one with a slight twist. It generates a random email for you rather than asking you to give your username & password (I don't want to handle securing people's usernames and emails at this stage). It makes an API call when the From Email matches the regex.
  Example from demo:
  
  URL: https://api.github.com/repos/idrissbellil/cryptomonitor/issues Method: POST (The HTTP Method: POST, GET, PUT, ..) From Regex: .* (only trigger the call given certain `From` emails so you it doesn't create a thousand tickets if somebody floods you with emails) Payload: {"title":"{{ .Subject }}","body":"{{ .Body }}","assignees":["idrissbellil"]} (the data part of the POST/PUT/even GET query - here you can re-use parts of the email you received like Subject, Body, To, From Headers: {"Accept":"application/vnd.github+json","Authorization":"Bearer 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","X-GitHub-Api-Version":"2022-11-28"}
  
  Okay, so, You're going to need to pretend like I'm 5 years old here.
  The end goal is for me to give this my email creds, it will then monitor my email and when I get a match it'll run the API call, right?
  However, right now, you don't want to take usernames and passwords so you generate random emails as an example to show what it COULD do.
  If I'm correct it might be a little early to give people access as there's nothing I can really do. I created an account on your site but there's nothing there explaining what I'm doing just a couple input boxes with a one word label.
  I would use this for email -> matrix but I'd have to self host it. I'm sure others would use it if you had some built in API calls that less techy people could use.
  Do you allow users to matched regex from the email and use it the API Call?
  
  The last example will be equivalent to the following curl:
  bash
  
  curl -L \ -X POST \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer github_pat_xxxx" \ -H "X-GitHub-Api-Version: 2022-11-28" \ https://api.github.com/repos/idrissbellil/cryptomonitor/issues \ -d '{"title":"Found a bug","body":"I'\''m having a problem with this.","assignees":["idrissbellil"]}'

Looks interesting, github will give the project a lot more visibility. If you want, you can make it a mirror of gitlab.

What would the benefit be of using this instead of let's say ActivePieces? Just kess resource usage or is there anything I'm missing?
- I have never heard of ActivePieces. I took 30 min now to review it and play with it.
  From that alone, I can say:
  you can definitely achieve what gossip does using ActivePieces (in other words, Gossip covers a small subset of what ActivityPieces does if you want to create your email manually and plug it into what they call an IMAP Piece)
  Yep, Gossip is much lighter and reacts instantly thanks to golang concurrency constructs (it's now running on a tiny VPS there are few jobs and it's consuming 22MB of RAM, I will be able to keep it free and scale really really high without much struggle)
  Gossip is geared more towards tech people (if you can put together a curl query to cover your needs than you can do almost anything you want - trigger a telegram msg, matrix chat, create a Jira ticket, ...)
  Gossip doesn't handle any complex automations now, it simply connects an email it generates into a webhook you input (that seems to cover all the use cases I needed in my workplace)

8 comments