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

Mastodon Notification Agent #1994

Open
lasagnacrab opened this issue Feb 7, 2023 · 0 comments
Open

Mastodon Notification Agent #1994

lasagnacrab opened this issue Feb 7, 2023 · 0 comments

Comments

@lasagnacrab
Copy link

Is your feature request related to a problem?

Since Twitter is shutting down their free API, I want to move my Tautulli Twitter notification bot to my Mastodon server. I've been able to get rudimentary functionality out of the Webhook agent to post to Mastodon by using the Status method (text post listing new title added to my server), but I'm running into the issue of additionally attaching poster images in my Status post.

It seems the Mastodon API requires you to use the Media method as a separate request that will upload the image to the Mastodon instance and assign it a 'media_id', which you can then reference in the Status update. I'm a beginner when it comes to JSON and API's so I'm not sure if I'm interpreting the docs correctly. Here's the relevant API documentation.

If anyone else has achieved a Mastodon integration with media attachments I'm happy to use a full Webhook agent solution. Just figured since Twitter is shutting down the API a dedicated Mastodon agent might be useful to many people.

What is your feature request?

The new Mastodon Notification Agent would look very similar to the Twitter agent. Space to configure the agent with the Mastodon Application Access Token/Secrets, a checkbox option to 'Include Poster Image' that will use the Image Hosting 3rd Party API settings in order to upload the image to the Mastodon server, and all the regular triggers and conditions.

Thanks for the consideration.

Are there any workarounds?

No response

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants