Skip to content
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.

Courier as a destination #1924

Open
tk26 opened this issue Jun 13, 2021 · 2 comments
Open

Courier as a destination #1924

tk26 opened this issue Jun 13, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@tk26
Copy link

tk26 commented Jun 13, 2021

Courier (https://www.courier.com/) provides a single API to manage the notification workflows. It would be great if Grouparoo could have Courier as a destination.

Courier provides Lists (https://docs.courier.com/reference/lists-api) and Profiles (https://docs.courier.com/reference/profiles-api) API - for companies using or wanting to use Courier, having a Grouparoo integration can help them sync the data from their data sources directly to Courier.

Disclaimer: I am a full-stack engineer at Courier - would also be totally down to contributing this feature myself.

@tk26 tk26 added the enhancement New feature or request label Jun 13, 2021
@bleonard
Copy link
Member

Hey @tk26, we'd love to get a contribution.
From the profile API, it looks like Courier takes an "external_id" approach, so recipient_id would be a required field in destination mappings.
Here's some documentation on how to make a destination plugin: https://www.grouparoo.com/docs/development/destinations

@tk26
Copy link
Author

tk26 commented Jun 14, 2021

Sounds great. Thanks @bleonard

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants