fix(rss): add top-level title, link, pubDate fields to RSS trigger output

[waleedlatif1]

Summary

• Fixed RSS trigger not exposing title, link, pubDate at top level
• Fixed IMAP trigger not exposing messageId, subject, from, etc. at top level
• Both triggers were nesting data under item/email but blocks expected flat structure
• Updated polling services and webhook handlers to preserve top-level fields
• Cleaned up unused _finalInput parameter in buildIntegrationTriggerOutput

Type of Change

• Bug fix

Testing

Tested manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Review	Updated (UTC)
docs	Skipped		Jan 20, 2026 5:59pm

[greptile-apps]

Greptile Summary

Fixed data structure issues in RSS and IMAP trigger outputs by exposing key fields at the top level instead of only nesting them under item and email properties.

Changes Made:

• RSS trigger: Added title, link, and pubDate as top-level fields in the webhook payload (in addition to nested item object)
• IMAP trigger: Added messageId, subject, from, to, cc, date, bodyText, bodyHtml, mailbox, hasAttachments, and attachments as top-level fields (in addition to nested email object)
• Webhook handlers: Updated formatWebhookInput in utils.server.ts to preserve top-level fields when formatting RSS and IMAP webhook inputs
• Cleanup: Removed unused _finalInput parameter from buildIntegrationTriggerOutput function

Why This Matters:
Workflow blocks expect flat access to trigger data. Previously, blocks had to access fields like item.title or email.subject, but the system expected direct access like title and subject. This change maintains backward compatibility by keeping the nested structure while adding top-level fields for proper block consumption.

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The changes are straightforward bug fixes that add top-level fields to webhook payloads without removing existing nested structures, ensuring backward compatibility. The implementation is consistent across both RSS and IMAP triggers, follows the established pattern, and includes a clean refactor of an unused parameter. No breaking changes or risky logic modifications are introduced.
• No files require special attention

Important Files Changed

Filename	Overview
apps/sim/executor/utils/start-block.ts	Removed unused _finalInput parameter from buildIntegrationTriggerOutput - clean refactor
apps/sim/lib/webhooks/rss-polling-service.ts	Added top-level title, link, pubDate fields to RSS payload for flat access by blocks
apps/sim/lib/webhooks/imap-polling-service.ts	Added top-level email fields (messageId, subject, from, etc.) to IMAP payload for flat access
apps/sim/lib/webhooks/utils.server.ts	Updated webhook formatters to preserve top-level fields for RSS and IMAP payloads

Sequence Diagram

sequenceDiagram
    participant Poller as RSS/IMAP Polling Service
    participant Webhook as Webhook Trigger Handler
    participant Format as formatWebhookInput
    participant Start as buildStartBlockOutput
    participant Block as Workflow Blocks
    
    Note over Poller: Poll for new items/emails
    Poller->>Poller: Create payload with top-level fields
    Note right of Poller: RSS: title, link, pubDate<br/>IMAP: messageId, subject, from, etc.
    Poller->>Webhook: POST /api/webhooks/trigger/{path}
    Webhook->>Format: Format webhook input
    Note right of Format: Preserves top-level fields<br/>+ nested item/email
    Format->>Start: Pass formatted input
    Start->>Start: buildIntegrationTriggerOutput(workflowInput)
    Note right of Start: Returns flat object<br/>(no processing needed)
    Start->>Block: Flat output with top-level fields
    Note right of Block: Blocks can now access<br/>title, link, pubDate directly

Loading

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.}

[waleedlatif1]

@greptile