Skip to content

feat: add Automations and Events endpoint support#97

Merged
drish merged 4 commits intomainfrom
feat/automations
Apr 10, 2026
Merged

feat: add Automations and Events endpoint support#97
drish merged 4 commits intomainfrom
feat/automations

Conversation

@christina-de-martinez
Copy link
Copy Markdown
Contributor

@christina-de-martinez christina-de-martinez commented Apr 9, 2026

Summary by cubic

Add full Automations and Events API support to the SDK so users can define, manage, and trigger workflows. Includes new models, client methods, and tests for end-to-end coverage.

  • New Features

    • Automations: create/update/retrieve/list (filter by status), stop, delete; list runs (filter by status) and retrieve a run. Models added for automations, graph steps/edges, and runs.
    • Events: create/retrieve (by id or name)/list/update/delete (by id or name), and send events with contact_id or email plus payload. Models added for events and send responses.
    • Client surface: new async methods on IResend with implementations in ResendClient (ResendClient.Automations.cs, ResendClient.Events.cs) for all endpoints. Tests and local mock controllers cover these flows.
  • Bug Fixes

    • Use key (not ref) for automation step identifiers in create/update payloads to match the API.
    • Mock: EventRetrieve response now reflects the route id/name to match the requested lookup.

Written for commit 7b48715. Summary will update on new commits.

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 26 files

Confidence score: 3/5

  • There is a concrete functional risk in tools/Resend.ApiServer/Controllers/EventController.cs: EventRetrieve ignores the route id and always returns a hard-coded event, so clients can receive incorrect data.
  • Given this is a user-facing API behavior bug with moderate severity/confidence, merge risk is moderate rather than high, but it should be corrected before relying on this endpoint.
  • Pay close attention to tools/Resend.ApiServer/Controllers/EventController.cs - ensure EventRetrieve uses the requested id to fetch and return the correct event.
Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="tools/Resend.ApiServer/Controllers/EventController.cs">

<violation number="1" location="tools/Resend.ApiServer/Controllers/EventController.cs:45">
P2: EventRetrieve ignores the `id` route parameter and always returns a hard-coded event, so callers cannot retrieve the event they requested.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

Comment thread tools/Resend.ApiServer/Controllers/EventController.cs Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants