improvement(wand): added more wands

[aadamgough]

Summary

Added more wand configs to unintuitive subblocks

Type of Change

• New feature

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 10, 2026 1:52am

[greptile-apps]

Greptile Overview

Greptile Summary

This PR enhances user experience by adding AI wand configurations to input fields across six integration blocks (Google Sheets, Microsoft Excel, SharePoint, Supabase, and Twilio Voice). The wands provide natural language assistance for generating complex inputs like spreadsheet ranges, JSON data structures, TwiML markup, and SQL expressions. SharePoint received the most extensive updates including template selection, column definitions, and list item fields.

Confidence Score: 4/5

• Safe to merge with minor naming consistency consideration in SharePoint
• All wand configurations follow established patterns from the codebase and provide comprehensive prompt instructions with clear examples. The changes are purely additive (no logic changes) and follow the existing wandConfig structure used throughout the codebase. One minor style issue in SharePoint where columnDefinitions field gets mapped to pageContent parameter creates a naming disconnect, but this won't cause functional issues.
• apps/sim/blocks/blocks/sharepoint.ts has a field naming inconsistency that could impact maintainability

Important Files Changed

File Analysis

Filename	Score	Overview
apps/sim/blocks/blocks/sharepoint.ts	3/5	Renamed pageContent field to columnDefinitions for create_list operation and added wands for listTemplate, columnDefinitions, and listItemFields; mapping columnDefinitions to pageContent in transform may cause confusion

Sequence Diagram

sequenceDiagram
    participant User
    participant UI as Block UI
    participant Wand as AI Wand
    participant API as Integration API
    
    User->>UI: "Enter natural language description"
    UI->>Wand: "Trigger wand with prompt template"
    Wand->>Wand: "Generate formatted output"
    Wand-->>UI: "Return structured data"
    UI->>API: "Send formatted parameters"
    API-->>User: "Execute operation"

Loading

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

The field ID pageContent is misleading and incorrect for column definitions. This field is used for SharePoint list column definitions (as shown by the title "Column Definitions" and the wandConfig prompt), but the ID suggests it's for page content.

This will cause issues because:

1. The field title says "Column Definitions" but the ID is pageContent
2. Looking at line 478, the inputs definition shows pageContent is described as "Page content" which doesn't match this usage
3. This creates confusion between page content (used in create_page operation) and column definitions (used in create_list operation)

Suggested change

	id: 'pageContent',
	title: 'Page Content',
	title: 'Column Definitions',
	id: 'columnDefinitions',
	title: 'Column Definitions',

This change should also be reflected in the inputs section and any param processing logic.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/sim/blocks/blocks/sharepoint.ts
Line: 168:169

Comment:
The field ID `pageContent` is misleading and incorrect for column definitions. This field is used for SharePoint list column definitions (as shown by the title "Column Definitions" and the wandConfig prompt), but the ID suggests it's for page content.

This will cause issues because:
1. The field title says "Column Definitions" but the ID is `pageContent`
2. Looking at line 478, the inputs definition shows `pageContent` is described as "Page content" which doesn't match this usage
3. This creates confusion between page content (used in create_page operation) and column definitions (used in create_list operation)

```suggestion
      id: 'columnDefinitions',
      title: 'Column Definitions',
```

This change should also be reflected in the inputs section and any param processing logic.

How can I resolve this? If you propose a fix, please make it concise.

[aadamgough]

@greptile

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

The field is named columnDefinitions in the UI but gets mapped to pageContent in the transform function (line 471). This creates a disconnect between the field name users see and the actual parameter name sent to the API. Consider either:

1. Keeping the field ID as pageContent and updating just the title/placeholder to be more descriptive
2. Or update the SharePoint tool/API to accept columnDefinitions as the parameter name instead of pageContent

This improves maintainability by keeping field IDs aligned with parameter names.

_{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/sim/blocks/blocks/sharepoint.ts
Line: 168:172

Comment:
The field is named `columnDefinitions` in the UI but gets mapped to `pageContent` in the transform function (line 471). This creates a disconnect between the field name users see and the actual parameter name sent to the API. Consider either:
1. Keeping the field ID as `pageContent` and updating just the title/placeholder to be more descriptive
2. Or update the SharePoint tool/API to accept `columnDefinitions` as the parameter name instead of `pageContent`

This improves maintainability by keeping field IDs aligned with parameter names.

<sub>Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!</sub>

How can I resolve this? If you propose a fix, please make it concise.