https://github.com/danesparza/plex2slack-lambda

:bell: Plex events => AWS Lambda => Slack notification
https://github.com/danesparza/plex2slack-lambda

api-gateway aws aws-lambda golang plex plex-media-server plex-webhooks slack slack-notifications slack-webhook slack-webhooks

Last synced: about 1 month ago
JSON representation

:bell: Plex events => AWS Lambda => Slack notification

• Host: GitHub
• URL: https://github.com/danesparza/plex2slack-lambda
• Owner: danesparza
• License: mit
• Created: 2019-10-27T13:04:07.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2019-10-27T21:52:34.000Z (about 5 years ago)
• Last Synced: 2024-06-20T11:52:32.296Z (7 months ago)
• Topics: api-gateway, aws, aws-lambda, golang, plex, plex-media-server, plex-webhooks, slack, slack-notifications, slack-webhook, slack-webhooks
• Language: Go
• Homepage:
• Size: 59.6 KB
• Stars: 2
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# plex2slack-lambda [![CircleCI](https://circleci.com/gh/danesparza/plex2slack-lambda.svg?style=shield)](https://circleci.com/gh/danesparza/plex2slack-lambda)

Golang based AWS Lambda handler for sending plex webhook messages to a slack channel.  For a standalone service, see [plex2slack](https://github.com/danesparza/plex2slack)

## Quick start

### AWS Lambda setup

- Download the latest release and setup a new Go based lambda function in AWS.  The handler name is `plex2slack-lambda`

- Add the environment variable `PLEX2SLACK_WEBHOOK_URL` to your lambda handler.  Set this to your Slack incoming webhook url.  It should look something like *https://hooks.slack.com/services/SOMETHING/SOMEID/SOMETHINGELSEHERE*

### AWS API Gateway setup

- Create a new AWS API Gateway API.  

- In the 'Settings' section for the AWS API Gateway for the new API, make sure to add `multipart/form-data` under *Binary Media Types*

- Create a resource (call it something like 'plex') and create a `POST` method on the resource.  Wire up the lambda handler on the method.  Make sure to select *Use Lambda Proxy integration*

- Deploy the API