You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.
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.
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
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.
The text was updated successfully, but these errors were encountered: