arcade-mcp/toolkits/salesforce/arcade_salesforce/tools/crm/contact.py
Sam Partee b6b4cd0a4c
🏗️ Restructure: Multi-Package Architecture + uv Migration (#412)
### Overview
Major restructuring from monolithic `arcade-ai` package to modular
library architecture with standardized uv-based dependency management.

![arcade-ai Monorepo
(2)](https://github.com/user-attachments/assets/25f102b0-bb87-4a04-9701-d227d05664b1)

### New Package Structure
- **`arcade-tdk`** - Lightweight toolkit development kit (core
decorators, auth)
- **`arcade-core`** - Core execution engine and catalog functionality  
- **`arcade-serve`** - FastAPI/MCP server components
- **`arcade-ai`** - Meta package that includes CLI functionality.
Optionally include evals via the `evals` extra. Optionally include all
packages via the `all` extra.

### Key Benefits
- **Lighter Dependencies**: Toolkits now depend only on `arcade-tdk` (~2
deps) vs full `arcade-ai` (~30+ deps)
- **Faster Builds**: uv provides 10-100x faster dependency resolution
and installation
- **Better Modularity**: Clear separation of concerns, consumers import
only what they need
- **Standard Tooling**: Eliminates custom poetry scripts, uses standard
Python packaging

### Migration Impact
- All 20 toolkits converted from poetry → uv with `arcade-tdk`
dependencies plus `arcade-ai[evals]` and `arcade-serve` dev
dependencies. When developing locally, devs should install toolkits via
`make install-local`.
- Modern Python 3.10+ type hints throughout
- Standardized build system with hatchling backend
- Enhanced Makefile with robust toolkit management commands
- Removed `arcade dev` CLI command
- Reduce the number of files created by `arcade new` and add an option
to not generate a tests and evals folder.

This foundation enables faster development cycles and cleaner dependency
chains for the growing toolkit ecosystem.

### Todo After this PR is merged
- [ ] Post-merge workflow(s) (release & publish containers, etc)
- [ ] Release order plan. @EricGustin suggests releasing in the
following order:
    1. `arcade-core` version 0.1.0
    2. `arcade-serve` version 0.1.0 and `arcade-tdk` version 0.1.0
    3. `arcade-ai` version 2.0.0
4. Patch release for all toolkits (all changes in toolkits are internal
refactors)
- [ ] [Update docs](https://github.com/ArcadeAI/docs/pull/318)

---------

Co-authored-by: Eric Gustin <eric@arcade.dev>
Co-authored-by: Eric Gustin <34000337+EricGustin@users.noreply.github.com>
2025-06-11 16:48:17 -07:00

64 lines
2.3 KiB
Python

from typing import Annotated
from arcade_tdk import ToolContext, tool
from arcade_tdk.auth import OAuth2
from arcade_tdk.errors import ToolExecutionError
from arcade_salesforce.exceptions import SalesforceToolExecutionError
from arcade_salesforce.models import SalesforceClient
# TODO: Add support for referencing an account by keywords (name, website, etc). We can use the
# get_account_data_by_keywords tool to search for accounts. If more than one is returned, we can
# raise a RetryableToolError providing the matches for the user to choose.
@tool(
requires_auth=OAuth2(
id="salesforce",
scopes=["write_contact"],
)
)
async def create_contact(
context: ToolContext,
account_id: Annotated[str, "The ID of the account to create the contact for."],
last_name: Annotated[str, "The last name of the contact."],
first_name: Annotated[str | None, "The first name of the contact."] = None,
email: Annotated[str | None, "The email of the contact."] = None,
phone: Annotated[str | None, "The phone number of the contact."] = None,
mobile_phone: Annotated[str | None, "The mobile phone number of the contact."] = None,
title: Annotated[
str | None,
"The title of the contact. E.g. 'CEO', 'Sales Director', 'CTO', etc.",
] = None,
department: Annotated[
str | None,
"The department of the contact. E.g. 'Marketing', 'Sales', 'IT', etc.",
] = None,
description: Annotated[str | None, "The description of the contact."] = None,
) -> Annotated[
dict,
"The created contact.",
]:
"""Creates a contact in Salesforce."""
if not last_name:
raise ToolExecutionError("Last name is required by Salesforce to create a contact.")
client = SalesforceClient(context.get_auth_token_or_empty())
contact = await client.create_contact(
account_id=account_id,
first_name=first_name,
last_name=last_name,
email=email,
phone=phone,
mobile_phone=mobile_phone,
title=title,
department=department,
description=description,
)
if not contact.get("success"):
raise SalesforceToolExecutionError(
message="Failed to create contact",
errors=contact.get("errors", []),
)
return {"success": True, "contactId": contact.get("id")}