PipedreamHQ / PipedreamHQ/pipedream

[APP]

Open
#21,283 0 comments 0 reactions 1 assignee Claimed by @sergio-eliot-rodriguez View on GitHub
app enhancement triaged
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

**Name of app / service**
MailKite

**Link to developer documentation**
https://mailkite.dev/docs/

**Is lack of support preventing you from moving forward, or do you have a workaround?**

I want to contribute the components myself — I have the API contracts mapped and the pd CLI set up. The blocker is just getting the mailkite app created in the registry with API-key auth (Authorization: Bearer ) so I can PR an inbound Source + a Send action against it.

**Are there specific actions or triggers you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!**

▎ Triggers (Sources)
▎ - New Inbound Email (Instant) — emit an event when an email arrives at a user's own verified domain (MailKite delivers a signed email.received webhook with parsed from/to/subject/text/html/threadId/auth/attachments). This is the gap today: Pipedream's built-in "New Email" trigger only gives a Pipedream-generated address — there's no first-class "email hit my domain → run this workflow" trigger.

▎ Actions
▎ - Send Email — send from a verified domain via POST /v1/send (to/cc/bcc, subject, html/text, reply-to, templates, attachments) → returns { id, status }.

▎ Likely follow-ups once the above land: Send with Template, Set/Update Webhook, Upload Attachment. I'll file these via the Action/Trigger templates.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.