Improvement(cc): added cc to gmail and outlook

[aadamgough]

Summary

Added cc to outlook and gmail

Type of Change

• New feature

Testing

Tested send and draft, both work.

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)

Screenshots/Videos

Screen.Recording.2025-08-07.at.1.31.10.PM.mov

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 8, 2025 8:27pm
sim	🛑 Canceled (Inspect)			Aug 8, 2025 8:27pm

[greptile-apps]

Greptile Summary

This PR adds CC (carbon copy) functionality to both Gmail and Outlook email integrations across the Sim platform. The changes span multiple layers of the application:

Backend Tool Implementation: The core email tools (gmail/send.ts, gmail/draft.ts, outlook/draft.ts) now accept an optional cc parameter that supports comma-separated email addresses. For Gmail, the implementation adds CC headers to the raw email format following RFC standards. For Outlook, a new parseEmails helper function converts comma-separated strings into the Microsoft Graph API's required recipient object format.

Type System Updates: The TypeScript interfaces (GmailSendParams, OutlookDraftParams) have been extended with optional cc fields, ensuring type safety throughout the application while maintaining backward compatibility.

UI Block Configuration: Both Gmail and Outlook block configurations now include CC input fields that appear conditionally when users select send or draft operations. These fields are positioned logically between the 'To' and 'Subject' fields, following standard email composition conventions.

Documentation Updates: The tool documentation files have been updated to reflect the new CC parameter availability, including proper parameter descriptions and usage examples.

The implementation maintains consistency between Gmail and Outlook integrations, with both supporting the same comma-separated format for multiple CC recipients. The optional nature of the CC parameter ensures existing workflows continue to function without modification.

Confidence score: 1/5

• This PR has a critical issue that will likely break the Outlook block functionality
• Score severely lowered due to duplicate CC field definitions in the Outlook block configuration that will cause UI conflicts
• Pay close attention to apps/sim/blocks/blocks/outlook.ts which contains duplicate field definitions at lines 58-64 and 106-114

_{9 files reviewed, 3 comments}

_{Edit Code Review Bot Settings | Greptile}

[greptile-apps]

style: Consider updating the EmailMetadata interface (lines 40-45) to include a cc field for consistency with the new parameter

[greptile-apps]

logic: Duplicate CC field definition detected. There are two cc fields defined (lines 58-64 and 106-114) which will cause configuration conflicts. Remove one of these duplicate definitions.

Suggested change

	{
	id: 'cc',
	title: 'CC',
	type: 'short-input',
	layout: 'full',
	placeholder: 'CC email address',
	condition: { field: 'operation', value: ['send_outlook', 'draft_outlook'] },
	},
	{
	id: 'cc',
	title: 'CC',
	type: 'short-input',
	layout: 'full',
	placeholder: 'CC recipients (comma-separated)',
	condition: { field: 'operation', value: ['send_outlook', 'draft_outlook'] },
	},

[greptile-apps]

style: Using any type reduces type safety. Consider defining a proper interface for the message structure

Context Used: Context - Avoid using type assertions to 'any' in TypeScript. Instead, ensure proper type definitions are used to maintain type safety. (link)

[waleedlatif1]

ket's update docs & rebase if need be and get this merged in @aadamgough