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)

you are viewing a single comment's thread
view the rest of the comments

[–] idriss@lemm.ee 2 points 2 days ago

All questions are welcome! By saying it's intended to tech people earlier I meant if you know what are the different components of an HTTP query, then you know enough to use it.

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?

That's not what I wanted to express. Not requesting your email credentials is an intended design decision (it's more challenging also). Because personally, if I was a user, I wouldn't feel comfortable giving my email credentials to a random website online. The alternative solution is to generate an email controlled by the website like I did.

So yeah, the intended use case isn't to monitor your email address. But rather give you an email address that you can plug in an alerting system for example that would result in a webhook call (that would notify you on matrix or telegram, create a github issue, create Jira ticket,..).

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.

Self hosting isn't necessary if you don't want to, you can already add your matrix webhook and generate a random email address you can use. You can configure your current gmail account for example to forward certain or all emails to that randomly generated address and that would trigger a webhook (matrix msg in our example). It involves an extra step (configuring gmail) at the benefit of not having to share your personal creds with a random website online (gossip).

I can provide an example on how to do that if you want to test that.

I do agree with you though on the second part, I will be adding some ready-to-use blocks for the most common services. That's already a planned feature.

Do you allow users to matched regex from the email and use it the API Call?

For now, it matches on the From Address only (to avoid spamming the API), but it will be very easy to add another field to match on the content or subject of the email if you think it's a worthy feature.