andre/crewAI
1
0
Fork 0
mirror of https://github.com/crewAIInc/crewAI.git synced 2026-01-08 23:58:34 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
Files
68c9990eefb59f57243ae83ff92f6a88e3838d30
crewAI/docs/pt-BR/enterprise/integrations/salesforce.mdx
Lorenze Jay d1343b96ed Release/v1.0.0 (#3618) 
* feat: add `apps` & `actions` attributes to Agent (#3504)

* feat: add app attributes to Agent

* feat: add actions attribute to Agent

* chore: resolve linter issues

* refactor: merge the apps and actions parameters into a single one

* fix: remove unnecessary print

* feat: logging error when CrewaiPlatformTools fails

* chore: export CrewaiPlatformTools directly from crewai_tools

* style: resolver linter issues

* test: fix broken tests

* style: solve linter issues

* fix: fix broken test

* feat: monorepo restructure and test/ci updates

- Add crewai workspace member
- Fix vcr cassette paths and restore test dirs
- Resolve ci failures and update linter/pytest rules

* chore: update python version to 3.13 and package metadata

* feat: add crewai-tools workspace and fix tests/dependencies

* feat: add crewai-tools workspace structure

* Squashed 'temp-crewai-tools/' content from commit 9bae5633

git-subtree-dir: temp-crewai-tools
git-subtree-split: 9bae56339096cb70f03873e600192bd2cd207ac9

* feat: configure crewai-tools workspace package with dependencies

* fix: apply ruff auto-formatting to crewai-tools code

* chore: update lockfile

* fix: don't allow tool tests yet

* fix: comment out extra pytest flags for now

* fix: remove conflicting conftest.py from crewai-tools tests

* fix: resolve dependency conflicts and test issues

- Pin vcrpy to 7.0.0 to fix pytest-recording compatibility
- Comment out types-requests to resolve urllib3 conflict
- Update requests requirement in crewai-tools to >=2.32.0

* chore: update CI workflows and docs for monorepo structure

* chore: update CI workflows and docs for monorepo structure

* fix: actions syntax

* chore: ci publish and pin versions

* fix: add permission to action

* chore: bump version to 1.0.0a1 across all packages

- Updated version to 1.0.0a1 in pyproject.toml for crewai and crewai-tools
- Adjusted version in __init__.py files for consistency

* WIP: v1 docs (#3626)

(cherry picked from commit d46e20fa09bcd2f5916282f5553ddeb7183bd92c)

* docs: parity for all translations

* docs: full name of acronym AMP

* docs: fix lingering unused code

* docs: expand contextual options in docs.json

* docs: add contextual action to request feature on GitHub (#3635)

* chore: apply linting fixes to crewai-tools

* feat: add required env var validation for brightdata

Co-authored-by: Greyson Lalonde <greyson.r.lalonde@gmail.com>

* fix: handle properly anyOf oneOf allOf schema's props

Co-authored-by: Greyson Lalonde <greyson.r.lalonde@gmail.com>

* feat: bump version to 1.0.0a2

* Lorenze/native inference sdks (#3619)

* ruff linted

* using native sdks with litellm fallback

* drop exa

* drop print on completion

* Refactor LLM and utility functions for type consistency

- Updated `max_tokens` parameter in `LLM` class to accept `float` in addition to `int`.
- Modified `create_llm` function to ensure consistent type hints and return types, now returning `LLM | BaseLLM | None`.
- Adjusted type hints for various parameters in `create_llm` and `_llm_via_environment_or_fallback` functions for improved clarity and type safety.
- Enhanced test cases to reflect changes in type handling and ensure proper instantiation of LLM instances.

* fix agent_tests

* fix litellm tests and usagemetrics fix

* drop print

* Refactor LLM event handling and improve test coverage

- Removed commented-out event emission for LLM call failures in `llm.py`.
- Added `from_agent` parameter to `CrewAgentExecutor` for better context in LLM responses.
- Enhanced test for LLM call failure to simulate OpenAI API failure and updated assertions for clarity.
- Updated agent and task ID assertions in tests to ensure they are consistently treated as strings.

* fix test_converter

* fixed tests/agents/test_agent.py

* Refactor LLM context length exception handling and improve provider integration

- Renamed `LLMContextLengthExceededException` to `LLMContextLengthExceededExceptionError` for clarity and consistency.
- Updated LLM class to pass the provider parameter correctly during initialization.
- Enhanced error handling in various LLM provider implementations to raise the new exception type.
- Adjusted tests to reflect the updated exception name and ensure proper error handling in context length scenarios.

* Enhance LLM context window handling across providers

- Introduced CONTEXT_WINDOW_USAGE_RATIO to adjust context window sizes dynamically for Anthropic, Azure, Gemini, and OpenAI LLMs.
- Added validation for context window sizes in Azure and Gemini providers to ensure they fall within acceptable limits.
- Updated context window size calculations to use the new ratio, improving consistency and adaptability across different models.
- Removed hardcoded context window sizes in favor of ratio-based calculations for better flexibility.

* fix test agent again

* fix test agent

* feat: add native LLM providers for Anthropic, Azure, and Gemini

- Introduced new completion implementations for Anthropic, Azure, and Gemini, integrating their respective SDKs.
- Added utility functions for tool validation and extraction to support function calling across LLM providers.
- Enhanced context window management and token usage extraction for each provider.
- Created a common utility module for shared functionality among LLM providers.

* chore: update dependencies and improve context management

- Removed direct dependency on `litellm` from the main dependencies and added it under extras for better modularity.
- Updated the `litellm` dependency specification to allow for greater flexibility in versioning.
- Refactored context length exception handling across various LLM providers to use a consistent error class.
- Enhanced platform-specific dependency markers for NVIDIA packages to ensure compatibility across different systems.

* refactor(tests): update LLM instantiation to include is_litellm flag in test cases

- Modified multiple test cases in test_llm.py to set the is_litellm parameter to True when instantiating the LLM class.
- This change ensures that the tests are aligned with the latest LLM configuration requirements and improves consistency across test scenarios.
- Adjusted relevant assertions and comments to reflect the updated LLM behavior.

* linter

* linted

* revert constants

* fix(tests): correct type hint in expected model description

- Updated the expected description in the test_generate_model_description_dict_field function to use 'Dict' instead of 'dict' for consistency with type hinting conventions.
- This change ensures that the test accurately reflects the expected output format for model descriptions.

* refactor(llm): enhance LLM instantiation and error handling

- Updated the LLM class to include validation for the model parameter, ensuring it is a non-empty string.
- Improved error handling by logging warnings when the native SDK fails, allowing for a fallback to LiteLLM.
- Adjusted the instantiation of LLM in test cases to consistently include the is_litellm flag, aligning with recent changes in LLM configuration.
- Modified relevant tests to reflect these updates, ensuring better coverage and accuracy in testing scenarios.

* fixed test

* refactor(llm): enhance token usage tracking and add copy methods

- Updated the LLM class to track token usage and log callbacks in streaming mode, improving monitoring capabilities.
- Introduced shallow and deep copy methods for the LLM instance, allowing for better management of LLM configurations and parameters.
- Adjusted test cases to instantiate LLM with the is_litellm flag, ensuring alignment with recent changes in LLM configuration.

* refactor(tests): reorganize imports and enhance error messages in test cases

- Cleaned up import statements in test_crew.py for better organization and readability.
- Enhanced error messages in test cases to use `re.escape` for improved regex matching, ensuring more robust error handling.
- Adjusted comments for clarity and consistency across test scenarios.
- Ensured that all necessary modules are imported correctly to avoid potential runtime issues.

* feat: add base devtooling

* fix: ensure dep refs are updated for devtools

* fix: allow pre-release

* feat: allow release after tag

* feat: bump versions to 1.0.0a3 

Co-authored-by: Greyson LaLonde <greyson.r.lalonde@gmail.com>

* fix: match tag and release title, ignore devtools build for pypi

* fix: allow failed pypi publish

* feat: introduce trigger listing and execution commands for local development (#3643)

* chore: exclude tests from ruff linting

* chore: exclude tests from GitHub Actions linter

* fix: replace print statements with logger in agent and memory handling

* chore: add noqa for intentional print in printer utility

* fix: resolve linting errors across codebase

* feat: update docs with new approach to consume Platform Actions (#3675)

* fix: remove duplicate line and add explicit env var

* feat: bump versions to 1.0.0a4 (#3686)

* Update triggers docs (#3678)

* docs: introduce triggers list & triggers run command

* docs: add KO triggers docs

* docs: ensure CREWAI_PLATFORM_INTEGRATION_TOKEN is mentioned on docs (#3687)

* Lorenze/bedrock llm (#3693)

* feat: add AWS Bedrock support and update dependencies

- Introduced BedrockCompletion class for AWS Bedrock integration in LLM.
- Added boto3 as a new dependency in both pyproject.toml and uv.lock.
- Updated LLM class to support Bedrock provider.
- Created new files for Bedrock provider implementation.

* using converse api

* converse

* linted

* refactor: update BedrockCompletion class to improve parameter handling

- Changed max_tokens from a fixed integer to an optional integer.
- Simplified model ID assignment by removing the inference profile mapping method.
- Cleaned up comments and unnecessary code related to tool specifications and model-specific parameters.

* feat: improve event bus thread safety and async support

Add thread-safe, async-compatible event bus with read–write locking and
handler dependency ordering. Remove blinker dependency and implement
direct dispatch. Improve type safety, error handling, and deterministic
event synchronization.

Refactor tests to auto-wait for async handlers, ensure clean teardown,
and add comprehensive concurrency coverage. Replace thread-local state
in AgentEvaluator with instance-based locking for correct cross-thread
access. Enhance tracing reliability and event finalization.

* feat: enhance OpenAICompletion class with additional client parameters (#3701)

* feat: enhance OpenAICompletion class with additional client parameters

- Added support for default_headers, default_query, and client_params in the OpenAICompletion class.
- Refactored client initialization to use a dedicated method for client parameter retrieval.
- Introduced new test cases to validate the correct usage of OpenAICompletion with various parameters.

* fix: correct test case for unsupported OpenAI model

- Updated the test_openai.py to ensure that the LLM instance is created before calling the method, maintaining proper error handling for unsupported models.
- This change ensures that the test accurately checks for the NotFoundError when an invalid model is specified.

* fix: enhance error handling in OpenAICompletion class

- Added specific exception handling for NotFoundError and APIConnectionError in the OpenAICompletion class to provide clearer error messages and improve logging.
- Updated the test case for unsupported models to ensure it raises a ValueError with the appropriate message when a non-existent model is specified.
- This change improves the robustness of the OpenAI API integration and enhances the clarity of error reporting.

* fix: improve test for unsupported OpenAI model handling

- Refactored the test case in test_openai.py to create the LLM instance after mocking the OpenAI client, ensuring proper error handling for unsupported models.
- This change enhances the clarity of the test by accurately checking for ValueError when a non-existent model is specified, aligning with recent improvements in error handling for the OpenAICompletion class.

* feat: bump versions to 1.0.0b1 (#3706)

* Lorenze/tools drop litellm (#3710)

* completely drop litellm and correctly pass config for qdrant

* feat: add support for additional embedding models in EmbeddingService

- Expanded the list of supported embedding models to include Google Vertex, Hugging Face, Jina, Ollama, OpenAI, Roboflow, Watson X, custom embeddings, Sentence Transformers, Text2Vec, OpenClip, and Instructor.
- This enhancement improves the versatility of the EmbeddingService by allowing integration with a wider range of embedding providers.

* fix: update collection parameter handling in CrewAIRagAdapter

- Changed the condition for setting vectors_config in the CrewAIRagAdapter to check for QdrantConfig instance instead of using hasattr. This improves type safety and ensures proper configuration handling for Qdrant integration.

* moved stagehand as optional dep (#3712)

* feat: bump versions to 1.0.0b2 (#3713)

* feat: enhance AnthropicCompletion class with additional client parame… (#3707)

* feat: enhance AnthropicCompletion class with additional client parameters and tool handling

- Added support for client_params in the AnthropicCompletion class to allow for additional client configuration.
- Refactored client initialization to use a dedicated method for retrieving client parameters.
- Implemented a new method to handle tool use conversation flow, ensuring proper execution and response handling.
- Introduced comprehensive test cases to validate the functionality of the AnthropicCompletion class, including tool use scenarios and parameter handling.

* drop print statements

* test: add fixture to mock ANTHROPIC_API_KEY for tests

- Introduced a pytest fixture to automatically mock the ANTHROPIC_API_KEY environment variable for all tests in the test_anthropic.py module.
- This change ensures that tests can run without requiring a real API key, improving test isolation and reliability.

* refactor: streamline streaming message handling in AnthropicCompletion class

- Removed the 'stream' parameter from the API call as it is set internally by the SDK.
- Simplified the handling of tool use events and response construction by extracting token usage from the final message.
- Enhanced the flow for managing tool use conversation, ensuring proper integration with the streaming API response.

* fix streaming here too

* fix: improve error handling in tool conversion for AnthropicCompletion class

- Enhanced exception handling during tool conversion by catching KeyError and ValueError.
- Added logging for conversion errors to aid in debugging and maintain robustness in tool integration.

* feat: enhance GeminiCompletion class with client parameter support (#3717)

* feat: enhance GeminiCompletion class with client parameter support

- Added support for client_params in the GeminiCompletion class to allow for additional client configuration.
- Refactored client initialization into a dedicated method for improved parameter handling.
- Introduced a new method to retrieve client parameters, ensuring compatibility with the base class.
- Enhanced error handling during client initialization to provide clearer messages for missing configuration.
- Updated documentation to reflect the changes in client parameter usage.

* add optional dependancies

* refactor: update test fixture to mock GOOGLE_API_KEY

- Renamed the fixture from `mock_anthropic_api_key` to `mock_google_api_key` to reflect the change in the environment variable being mocked.
- This update ensures that all tests in the module can run with a mocked GOOGLE_API_KEY, improving test isolation and reliability.

* fix tests

* feat: enhance BedrockCompletion class with advanced features

* feat: enhance BedrockCompletion class with advanced features and error handling

- Added support for guardrail configuration, additional model request fields, and custom response field paths in the BedrockCompletion class.
- Improved error handling for AWS exceptions and added token usage tracking with stop reason logging.
- Enhanced streaming response handling with comprehensive event management, including tool use and content block processing.
- Updated documentation to reflect new features and initialization parameters.
- Introduced a new test suite for BedrockCompletion to validate functionality and ensure robust integration with AWS Bedrock APIs.

* chore: add boto typing

* fix: use typing_extensions.Required for Python 3.10 compatibility

---------

Co-authored-by: Greyson Lalonde <greyson.r.lalonde@gmail.com>

* feat: azure native tests

* feat: add Azure AI Inference support and related tests

- Introduced the `azure-ai-inference` package with version `1.0.0b9` and its dependencies in `uv.lock` and `pyproject.toml`.
- Added new test files for Azure LLM functionality, including tests for Azure completion and tool handling.
- Implemented comprehensive test cases to validate Azure-specific behavior and integration with the CrewAI framework.
- Enhanced the testing framework to mock Azure credentials and ensure proper isolation during tests.

* feat: enhance AzureCompletion class with Azure OpenAI support

- Added support for the Azure OpenAI endpoint in the AzureCompletion class, allowing for flexible endpoint configurations.
- Implemented endpoint validation and correction to ensure proper URL formats for Azure OpenAI deployments.
- Enhanced error handling to provide clearer messages for common HTTP errors, including authentication and rate limit issues.
- Updated tests to validate the new endpoint handling and error messaging, ensuring robust integration with Azure AI Inference.
- Refactored parameter preparation to conditionally include the model parameter based on the endpoint type.

* refactor: convert project module to metaclass with full typing

* Lorenze/OpenAI base url backwards support (#3723)

* fix: enhance OpenAICompletion class base URL handling

- Updated the base URL assignment in the OpenAICompletion class to prioritize the new `api_base` attribute and fallback to the environment variable `OPENAI_BASE_URL` if both are not set.
- Added `api_base` to the list of parameters in the OpenAICompletion class to ensure proper configuration and flexibility in API endpoint management.

* feat: enhance OpenAICompletion class with api_base support

- Added the `api_base` parameter to the OpenAICompletion class to allow for flexible API endpoint configuration.
- Updated the `_get_client_params` method to prioritize `base_url` over `api_base`, ensuring correct URL handling.
- Introduced comprehensive tests to validate the behavior of `api_base` and `base_url` in various scenarios, including environment variable fallback.
- Enhanced test coverage for client parameter retrieval, ensuring robust integration with the OpenAI API.

* fix: improve OpenAICompletion class configuration handling

- Added a debug print statement to log the client configuration parameters during initialization for better traceability.
- Updated the base URL assignment logic to ensure it defaults to None if no valid base URL is provided, enhancing robustness in API endpoint configuration.
- Refined the retrieval of the `api_base` environment variable to streamline the configuration process.

* drop print

* feat: improvements on import native sdk support (#3725)

* feat: add support for Anthropic provider and enhance logging

- Introduced the `anthropic` package with version `0.69.0` in `pyproject.toml` and `uv.lock`, allowing for integration with the Anthropic API.
- Updated logging in the LLM class to provide clearer error messages when importing native providers, enhancing debugging capabilities.
- Improved error handling in the AnthropicCompletion class to guide users on installation via the updated error message format.
- Refactored import error handling in other provider classes to maintain consistency in error messaging and installation instructions.

* feat: enhance LLM support with Bedrock provider and update dependencies

- Added support for the `bedrock` provider in the LLM class, allowing integration with AWS Bedrock APIs.
- Updated `uv.lock` to replace `boto3` with `bedrock` in the dependencies, reflecting the new provider structure.
- Introduced `SUPPORTED_NATIVE_PROVIDERS` to include `bedrock` and ensure proper error handling when instantiating native providers.
- Enhanced error handling in the LLM class to raise informative errors when native provider instantiation fails.
- Added tests to validate the behavior of the new Bedrock provider and ensure fallback mechanisms work correctly for unsupported providers.

* test: update native provider fallback tests to expect ImportError

* adjust the test with the expected bevaior - raising ImportError

* this is exoecting the litellm format, all gemini native tests are in test_google.py

---------

Co-authored-by: Greyson LaLonde <greyson.r.lalonde@gmail.com>

* fix: remove stdout prints, improve test determinism, and update trace handling

Removed `print` statements from the `LLMStreamChunkEvent` handler to prevent
LLM response chunks from being written directly to stdout. The listener now
only tracks chunks internally.

Fixes #3715

Added explicit return statements for trace-related tests.

Updated cassette for `test_failed_evaluation` to reflect new behavior where
an empty trace dict is used instead of returning early.

Ensured deterministic cleanup order in test fixtures by making
`clear_event_bus_handlers` depend on `setup_test_environment`. This guarantees
event bus shutdown and file handle cleanup occur before temporary directory
deletion, resolving intermittent “Directory not empty” errors in CI.

* chore: remove lib/crewai exclusion from pre-commit hooks

* feat: enhance task guardrail functionality and validation

* feat: enhance task guardrail functionality and validation

- Introduced support for multiple guardrails in the Task class, allowing for sequential processing of guardrails.
- Added a new `guardrails` field to the Task model to accept a list of callable guardrails or string descriptions.
- Implemented validation to ensure guardrails are processed correctly, including handling of retries and error messages.
- Enhanced the `_invoke_guardrail_function` method to manage guardrail execution and integrate with existing task output processing.
- Updated tests to cover various scenarios involving multiple guardrails, including success, failure, and retry mechanisms.

This update improves the flexibility and robustness of task execution by allowing for more complex validation scenarios.

* refactor: enhance guardrail type handling in Task model

- Updated the Task class to improve guardrail type definitions, introducing GuardrailType and GuardrailsType for better clarity and type safety.
- Simplified the validation logic for guardrails, ensuring that both single and multiple guardrails are processed correctly.
- Enhanced error messages for guardrail validation to provide clearer feedback when incorrect types are provided.
- This refactor improves the maintainability and robustness of task execution by standardizing guardrail handling.

* feat: implement per-guardrail retry tracking in Task model

- Introduced a new private attribute `_guardrail_retry_counts` to the Task class for tracking retry attempts on a per-guardrail basis.
- Updated the guardrail processing logic to utilize the new retry tracking, allowing for independent retry counts for each guardrail.
- Enhanced error handling to provide clearer feedback when guardrails fail validation after exceeding retry limits.
- Modified existing tests to validate the new retry tracking behavior, ensuring accurate assertions on guardrail retries.

This update improves the robustness and flexibility of task execution by allowing for more granular control over guardrail validation and retry mechanisms.

* chore: 1.0.0b3 bump (#3734)

* chore: full ruff and mypy

improved linting, pre-commit setup, and internal architecture. Configured Ruff to respect .gitignore, added stricter rules, and introduced a lock pre-commit hook with virtualenv activation. Fixed type shadowing in EXASearchTool using a type_ alias to avoid PEP 563 conflicts and resolved circular imports in agent executor and guardrail modules. Removed agent-ops attributes, deprecated watson alias, and dropped crewai-enterprise tools with corresponding test updates. Refactored cache and memoization for thread safety and cleaned up structured output adapters and related logic.

* New MCL DSL (#3738)

* Adding MCP implementation

* New tests for MCP implementation

* fix tests

* update docs

* Revert "New tests for MCP implementation"

This reverts commit 0bbe6dee90.

* linter

* linter

* fix

* verify mcp pacakge exists

* adjust docs to be clear only remote servers are supported

* reverted

* ensure args schema generated properly

* properly close out

---------

Co-authored-by: lorenzejay <lorenzejaytech@gmail.com>
Co-authored-by: Greyson Lalonde <greyson.r.lalonde@gmail.com>

* feat: a2a experimental

experimental a2a support

---------

Co-authored-by: Lucas Gomide <lucaslg200@gmail.com>
Co-authored-by: Greyson LaLonde <greyson.r.lalonde@gmail.com>
Co-authored-by: Tony Kipkemboi <iamtonykipkemboi@gmail.com>
Co-authored-by: Mike Plachta <mplachta@users.noreply.github.com>
Co-authored-by: João Moura <joaomdmoura@gmail.com>
2025-10-20 14:10:19 -07:00

617 lines
28 KiB
Plaintext
Raw Blame History

---
title: Integração com Salesforce
description: "Automação de vendas e CRM com integração Salesforce para CrewAI."
icon: "salesforce"
mode: "wide"
---
## Visão Geral
Permita que seus agentes gerenciem relacionamentos com clientes, processos de vendas e dados através do Salesforce. Crie e atualize registros, gerencie leads e oportunidades, execute consultas SOQL e otimize seus fluxos de trabalho de CRM com automação potencializada por IA.
## Pré-requisitos
Antes de usar a integração Salesforce, certifique-se de que você possui:
- Uma conta [CrewAI AMP](https://app.crewai.com) com assinatura ativa
- Uma conta Salesforce com permissões apropriadas
- Sua conta Salesforce conectada via a [página de Integrações](https://app.crewai.com/integrations)
## Ferramentas Disponíveis
### **Gerenciamento de Registros**
<AccordionGroup>
<Accordion title="salesforce/create_record_contact">
**Descrição:** Crie um novo registro de Contato no Salesforce.
**Parâmetros:**
- `FirstName` (string, opcional): Primeiro nome
- `LastName` (string, obrigatório): Sobrenome - Este campo é obrigatório
- `accountId` (string, opcional): ID da Conta - Conta à qual o contato pertence
- `Email` (string, opcional): Endereço de e-mail
- `Title` (string, opcional): Cargo do contato, como CEO ou Vice-presidente
- `Description` (string, opcional): Descrição do contato
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Contato
</Accordion>
<Accordion title="salesforce/create_record_lead">
**Descrição:** Crie um novo registro de Lead no Salesforce.
**Parâmetros:**
- `FirstName` (string, opcional): Primeiro nome
- `LastName` (string, obrigatório): Sobrenome - Este campo é obrigatório
- `Company` (string, obrigatório): Empresa - Este campo é obrigatório
- `Email` (string, opcional): Endereço de e-mail
- `Phone` (string, opcional): Número de telefone
- `Website` (string, opcional): URL do site
- `Title` (string, opcional): Cargo do contato, como CEO ou Vice-presidente
- `Status` (string, opcional): Status do Lead - Use as Configurações de Workflow do Connect Portal para selecionar o status do Lead
- `Description` (string, opcional): Descrição do lead
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Lead
</Accordion>
<Accordion title="salesforce/create_record_opportunity">
**Descrição:** Crie um novo registro de Oportunidade no Salesforce.
**Parâmetros:**
- `Name` (string, obrigatório): Nome da Oportunidade - Este campo é obrigatório
- `StageName` (string, opcional): Estágio da Oportunidade - Use as Configurações de Workflow do Connect Portal para selecionar o estágio
- `CloseDate` (string, opcional): Data de fechamento no formato YYYY-MM-DD - Padrão para 30 dias a partir da data atual
- `AccountId` (string, opcional): Conta à qual a Oportunidade pertence
- `Amount` (string, opcional): Valor total estimado da venda
- `Description` (string, opcional): Descrição da oportunidade
- `OwnerId` (string, opcional): Usuário Salesforce designado para esta Oportunidade
- `NextStep` (string, opcional): Descrição da próxima tarefa no fechamento da Oportunidade
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Oportunidade
</Accordion>
<Accordion title="salesforce/create_record_task">
**Descrição:** Crie um novo registro de Tarefa no Salesforce.
**Parâmetros:**
- `whatId` (string, opcional): Relacionado ao ID - ID da Conta ou Oportunidade relacionada à Tarefa
- `whoId` (string, opcional): ID do Nome - ID do Contato ou Lead relacionado à Tarefa
- `subject` (string, obrigatório): Assunto da tarefa
- `activityDate` (string, opcional): Data da Atividade no formato YYYY-MM-DD
- `description` (string, opcional): Descrição da tarefa
- `taskSubtype` (string, obrigatório): Subtipo da Tarefa - Opções: task, email, listEmail, call
- `Status` (string, opcional): Status - Opções: Not Started, In Progress, Completed
- `ownerId` (string, opcional): ID do responsável - Usuário Salesforce designado para a Tarefa
- `callDurationInSeconds` (string, opcional): Duração da chamada em segundos
- `isReminderSet` (boolean, opcional): Se o lembrete está definido
- `reminderDateTime` (string, opcional): Data/Hora do lembrete no formato ISO
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Tarefa
</Accordion>
<Accordion title="salesforce/create_record_account">
**Descrição:** Crie um novo registro de Conta no Salesforce.
**Parâmetros:**
- `Name` (string, obrigatório): Nome da Conta - Este campo é obrigatório
- `OwnerId` (string, opcional): Usuário Salesforce responsável por esta Conta
- `Website` (string, opcional): URL do site
- `Phone` (string, opcional): Número de telefone
- `Description` (string, opcional): Descrição da conta
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Conta
</Accordion>
<Accordion title="salesforce/create_record_any">
**Descrição:** Crie um registro de qualquer tipo de objeto no Salesforce.
**Nota:** Esta é uma ferramenta flexível para criar registros de tipos de objetos personalizados ou desconhecidos.
</Accordion>
</AccordionGroup>
### **Atualização de Registros**
<AccordionGroup>
<Accordion title="salesforce/update_record_contact">
**Descrição:** Atualize um registro de Contato existente no Salesforce.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro a ser atualizado
- `FirstName` (string, opcional): Primeiro nome
- `LastName` (string, opcional): Sobrenome
- `accountId` (string, opcional): ID da Conta à qual o contato pertence
- `Email` (string, opcional): Endereço de e-mail
- `Title` (string, opcional): Cargo do contato
- `Description` (string, opcional): Descrição do contato
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Contato
</Accordion>
<Accordion title="salesforce/update_record_lead">
**Descrição:** Atualize um registro de Lead existente no Salesforce.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro a ser atualizado
- `FirstName` (string, opcional): Primeiro nome
- `LastName` (string, opcional): Sobrenome
- `Company` (string, opcional): Nome da empresa
- `Email` (string, opcional): Endereço de e-mail
- `Phone` (string, opcional): Número de telefone
- `Website` (string, opcional): URL do site
- `Title` (string, opcional): Cargo do contato
- `Status` (string, opcional): Status do Lead
- `Description` (string, opcional): Descrição do lead
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Lead
</Accordion>
<Accordion title="salesforce/update_record_opportunity">
**Descrição:** Atualize um registro de Oportunidade existente no Salesforce.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro a ser atualizado
- `Name` (string, opcional): Nome da Oportunidade
- `StageName` (string, opcional): Estágio da oportunidade
- `CloseDate` (string, opcional): Data de fechamento no formato YYYY-MM-DD
- `AccountId` (string, opcional): Conta à qual a Oportunidade pertence
- `Amount` (string, opcional): Valor total estimado da venda
- `Description` (string, opcional): Descrição da oportunidade
- `OwnerId` (string, opcional): Usuário Salesforce responsável por esta Oportunidade
- `NextStep` (string, opcional): Descrição da próxima tarefa no fechamento da Oportunidade
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Oportunidade
</Accordion>
<Accordion title="salesforce/update_record_task">
**Descrição:** Atualize um registro de Tarefa existente no Salesforce.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro a ser atualizado
- `whatId` (string, opcional): Relacionado ao ID - ID da Conta ou Oportunidade relacionada
- `whoId` (string, opcional): ID do Nome - ID do Contato ou Lead relacionado à Tarefa
- `subject` (string, opcional): Assunto da tarefa
- `activityDate` (string, opcional): Data da Atividade no formato YYYY-MM-DD
- `description` (string, opcional): Descrição da tarefa
- `Status` (string, opcional): Status - Opções: Not Started, In Progress, Completed
- `ownerId` (string, opcional): ID do responsável - Usuário Salesforce designado para a Tarefa
- `callDurationInSeconds` (string, opcional): Duração da chamada em segundos
- `isReminderSet` (boolean, opcional): Se o lembrete está definido
- `reminderDateTime` (string, opcional): Data/Hora do lembrete em formato ISO
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Tarefa
</Accordion>
<Accordion title="salesforce/update_record_account">
**Descrição:** Atualize um registro de Conta existente no Salesforce.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro a ser atualizado
- `Name` (string, opcional): Nome da Conta
- `OwnerId` (string, opcional): Usuário Salesforce responsável por esta Conta
- `Website` (string, opcional): URL do site
- `Phone` (string, opcional): Número de telefone
- `Description` (string, opcional): Descrição da conta
- `additionalFields` (object, opcional): Campos adicionais no formato JSON para campos personalizados de Conta
</Accordion>
<Accordion title="salesforce/update_record_any">
**Descrição:** Atualize um registro de qualquer tipo de objeto no Salesforce.
**Nota:** Esta é uma ferramenta flexível para atualizar registros de tipos de objetos personalizados ou desconhecidos.
</Accordion>
</AccordionGroup>
### **Recuperação de Registros**
<AccordionGroup>
<Accordion title="salesforce/get_record_by_id_contact">
**Descrição:** Obtenha um registro de Contato pelo seu ID.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro do Contato
</Accordion>
<Accordion title="salesforce/get_record_by_id_lead">
**Descrição:** Obtenha um registro de Lead pelo seu ID.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro do Lead
</Accordion>
<Accordion title="salesforce/get_record_by_id_opportunity">
**Descrição:** Obtenha um registro de Oportunidade pelo seu ID.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro da Oportunidade
</Accordion>
<Accordion title="salesforce/get_record_by_id_task">
**Descrição:** Obtenha um registro de Tarefa pelo seu ID.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro da Tarefa
</Accordion>
<Accordion title="salesforce/get_record_by_id_account">
**Descrição:** Obtenha um registro de Conta pelo seu ID.
**Parâmetros:**
- `recordId` (string, obrigatório): ID do registro da Conta
</Accordion>
<Accordion title="salesforce/get_record_by_id_any">
**Descrição:** Obtenha um registro de qualquer tipo de objeto pelo seu ID.
**Parâmetros:**
- `recordType` (string, obrigatório): Tipo do registro (ex.: "CustomObject__c")
- `recordId` (string, obrigatório): ID do registro
</Accordion>
</AccordionGroup>
### **Busca de Registros**
<AccordionGroup>
<Accordion title="salesforce/search_records_contact">
**Descrição:** Pesquise registros de Contato com filtragem avançada.
**Parâmetros:**
- `filterFormula` (object, opcional): Filtro avançado em forma normal disjuntiva com operadores específicos de campo
- `sortBy` (string, opcional): Campo para ordenação (ex.: "CreatedDate")
- `sortDirection` (string, opcional): Direção da ordenação - Opções: ASC, DESC
- `includeAllFields` (boolean, opcional): Incluir todos os campos nos resultados
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/search_records_lead">
**Descrição:** Pesquise registros de Lead com filtragem avançada.
**Parâmetros:**
- `filterFormula` (object, opcional): Filtro avançado em forma normal disjuntiva com operadores específicos de campo
- `sortBy` (string, opcional): Campo para ordenação (ex.: "CreatedDate")
- `sortDirection` (string, opcional): Direção da ordenação - Opções: ASC, DESC
- `includeAllFields` (boolean, opcional): Incluir todos os campos nos resultados
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/search_records_opportunity">
**Descrição:** Pesquise registros de Oportunidade com filtragem avançada.
**Parâmetros:**
- `filterFormula` (object, opcional): Filtro avançado em forma normal disjuntiva com operadores específicos de campo
- `sortBy` (string, opcional): Campo para ordenação (ex.: "CreatedDate")
- `sortDirection` (string, opcional): Direção da ordenação - Opções: ASC, DESC
- `includeAllFields` (boolean, opcional): Incluir todos os campos nos resultados
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/search_records_task">
**Descrição:** Pesquise registros de Tarefa com filtragem avançada.
**Parâmetros:**
- `filterFormula` (object, opcional): Filtro avançado em forma normal disjuntiva com operadores específicos de campo
- `sortBy` (string, opcional): Campo para ordenação (ex.: "CreatedDate")
- `sortDirection` (string, opcional): Direção da ordenação - Opções: ASC, DESC
- `includeAllFields` (boolean, opcional): Incluir todos os campos nos resultados
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/search_records_account">
**Descrição:** Pesquise registros de Conta com filtragem avançada.
**Parâmetros:**
- `filterFormula` (object, opcional): Filtro avançado em forma normal disjuntiva com operadores específicos de campo
- `sortBy` (string, opcional): Campo para ordenação (ex.: "CreatedDate")
- `sortDirection` (string, opcional): Direção da ordenação - Opções: ASC, DESC
- `includeAllFields` (boolean, opcional): Incluir todos os campos nos resultados
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/search_records_any">
**Descrição:** Pesquise registros de qualquer tipo de objeto.
**Parâmetros:**
- `recordType` (string, obrigatório): Tipo de registro para buscar
- `filterFormula` (string, opcional): Critérios de busca por filtro
- `includeAllFields` (boolean, opcional): Incluir todos os campos nos resultados
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
</AccordionGroup>
### **Recuperação por List View**
<AccordionGroup>
<Accordion title="salesforce/get_record_by_view_id_contact">
**Descrição:** Obtenha registros de Contato de um List View específico.
**Parâmetros:**
- `listViewId` (string, obrigatório): ID do List View
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/get_record_by_view_id_lead">
**Descrição:** Obtenha registros de Lead de um List View específico.
**Parâmetros:**
- `listViewId` (string, obrigatório): ID do List View
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/get_record_by_view_id_opportunity">
**Descrição:** Obtenha registros de Oportunidade de um List View específico.
**Parâmetros:**
- `listViewId` (string, obrigatório): ID do List View
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/get_record_by_view_id_task">
**Descrição:** Obtenha registros de Tarefa de um List View específico.
**Parâmetros:**
- `listViewId` (string, obrigatório): ID do List View
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/get_record_by_view_id_account">
**Descrição:** Obtenha registros de Conta de um List View específico.
**Parâmetros:**
- `listViewId` (string, obrigatório): ID do List View
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
<Accordion title="salesforce/get_record_by_view_id_any">
**Descrição:** Obtenha registros de qualquer tipo de objeto a partir de um List View específico.
**Parâmetros:**
- `recordType` (string, obrigatório): Tipo do registro
- `listViewId` (string, obrigatório): ID do List View
- `paginationParameters` (object, opcional): Configurações de paginação com pageCursor
</Accordion>
</AccordionGroup>
### **Campos Personalizados**
<AccordionGroup>
<Accordion title="salesforce/create_custom_field_contact">
**Descrição:** Crie campos personalizados para objetos de Contato.
**Parâmetros:**
- `label` (string, obrigatório): Rótulo do campo para exibições e referência interna
- `type` (string, obrigatório): Tipo do campo - Opções: Checkbox, Currency, Date, Email, Number, Percent, Phone, Picklist, MultiselectPicklist, Text, TextArea, LongTextArea, Html, Time, Url
- `defaultCheckboxValue` (boolean, opcional): Valor padrão para campos checkbox
- `length` (string, obrigatório): Comprimento para campos numéricos/texto
- `decimalPlace` (string, obrigatório): Casas decimais para campos numéricos
- `pickListValues` (string, obrigatório): Valores para campos picklist (separados por novas linhas)
- `visibleLines` (string, obrigatório): Linhas visíveis para campos multiseleção/área de texto
- `description` (string, opcional): Descrição do campo
- `helperText` (string, opcional): Texto de ajuda exibido ao passar o mouse
- `defaultFieldValue` (string, opcional): Valor padrão do campo
</Accordion>
<Accordion title="salesforce/create_custom_field_lead">
**Descrição:** Crie campos personalizados para objetos de Lead.
**Parâmetros:**
- `label` (string, obrigatório): Rótulo do campo para exibições e referência interna
- `type` (string, obrigatório): Tipo do campo - Opções: Checkbox, Currency, Date, Email, Number, Percent, Phone, Picklist, MultiselectPicklist, Text, TextArea, LongTextArea, Html, Time, Url
- `defaultCheckboxValue` (boolean, opcional): Valor padrão para campos checkbox
- `length` (string, obrigatório): Comprimento para campos numéricos/texto
- `decimalPlace` (string, obrigatório): Casas decimais para campos numéricos
- `pickListValues` (string, obrigatório): Valores para campos picklist (separados por novas linhas)
- `visibleLines` (string, obrigatório): Linhas visíveis para campos multiseleção/área de texto
- `description` (string, opcional): Descrição do campo
- `helperText` (string, opcional): Texto de ajuda exibido ao passar o mouse
- `defaultFieldValue` (string, opcional): Valor padrão do campo
</Accordion>
<Accordion title="salesforce/create_custom_field_opportunity">
**Descrição:** Crie campos personalizados para objetos de Oportunidade.
**Parâmetros:**
- `label` (string, obrigatório): Rótulo do campo para exibições e referência interna
- `type` (string, obrigatório): Tipo do campo - Opções: Checkbox, Currency, Date, Email, Number, Percent, Phone, Picklist, MultiselectPicklist, Text, TextArea, LongTextArea, Html, Time, Url
- `defaultCheckboxValue` (boolean, opcional): Valor padrão para campos checkbox
- `length` (string, obrigatório): Comprimento para campos numéricos/texto
- `decimalPlace` (string, obrigatório): Casas decimais para campos numéricos
- `pickListValues` (string, obrigatório): Valores para campos picklist (separados por novas linhas)
- `visibleLines` (string, obrigatório): Linhas visíveis para campos multiseleção/área de texto
- `description` (string, opcional): Descrição do campo
- `helperText` (string, opcional): Texto de ajuda exibido ao passar o mouse
- `defaultFieldValue` (string, opcional): Valor padrão do campo
</Accordion>
<Accordion title="salesforce/create_custom_field_task">
**Descrição:** Crie campos personalizados para objetos de Tarefa.
**Parâmetros:**
- `label` (string, obrigatório): Rótulo do campo para exibições e referência interna
- `type` (string, obrigatório): Tipo do campo - Opções: Checkbox, Currency, Date, Email, Number, Percent, Phone, Picklist, MultiselectPicklist, Text, TextArea, Time, Url
- `defaultCheckboxValue` (boolean, opcional): Valor padrão para campos checkbox
- `length` (string, obrigatório): Comprimento para campos numéricos/texto
- `decimalPlace` (string, obrigatório): Casas decimais para campos numéricos
- `pickListValues` (string, obrigatório): Valores para campos picklist (separados por novas linhas)
- `visibleLines` (string, obrigatório): Linhas visíveis para campos multiseleção
- `description` (string, opcional): Descrição do campo
- `helperText` (string, opcional): Texto de ajuda exibido ao passar o mouse
- `defaultFieldValue` (string, opcional): Valor padrão do campo
</Accordion>
<Accordion title="salesforce/create_custom_field_account">
**Descrição:** Crie campos personalizados para objetos de Conta.
**Parâmetros:**
- `label` (string, obrigatório): Rótulo do campo para exibições e referência interna
- `type` (string, obrigatório): Tipo do campo - Opções: Checkbox, Currency, Date, Email, Number, Percent, Phone, Picklist, MultiselectPicklist, Text, TextArea, LongTextArea, Html, Time, Url
- `defaultCheckboxValue` (boolean, opcional): Valor padrão para campos checkbox
- `length` (string, obrigatório): Comprimento para campos numéricos/texto
- `decimalPlace` (string, obrigatório): Casas decimais para campos numéricos
- `pickListValues` (string, obrigatório): Valores para campos picklist (separados por novas linhas)
- `visibleLines` (string, obrigatório): Linhas visíveis para campos multiseleção/área de texto
- `description` (string, opcional): Descrição do campo
- `helperText` (string, opcional): Texto de ajuda exibido ao passar o mouse
- `defaultFieldValue` (string, opcional): Valor padrão do campo
</Accordion>
<Accordion title="salesforce/create_custom_field_any">
**Descrição:** Crie campos personalizados para qualquer tipo de objeto.
**Nota:** Esta é uma ferramenta flexível para criar campos personalizados para tipos de objetos personalizados ou desconhecidos.
</Accordion>
</AccordionGroup>
### **Operações Avançadas**
<AccordionGroup>
<Accordion title="salesforce/write_soql_query">
**Descrição:** Execute consultas SOQL personalizadas em seus dados do Salesforce.
**Parâmetros:**
- `query` (string, obrigatório): Consulta SOQL (ex.: "SELECT Id, Name FROM Account WHERE Name = 'Exemplo'")
</Accordion>
<Accordion title="salesforce/create_custom_object">
**Descrição:** Crie um novo objeto personalizado no Salesforce.
**Parâmetros:**
- `label` (string, obrigatório): Rótulo do objeto para abas, layouts de página e relatórios
- `pluralLabel` (string, obrigatório): Rótulo plural (ex.: "Contas")
- `description` (string, opcional): Uma descrição do Objeto Personalizado
- `recordName` (string, obrigatório): Nome do registro exibido em layouts e buscas (ex.: "Nome da Conta")
</Accordion>
<Accordion title="salesforce/describe_action_schema">
**Descrição:** Obtenha o schema esperado para operações em tipos de objetos específicos.
**Parâmetros:**
- `recordType` (string, obrigatório): Tipo de registro a ser detalhado
- `operation` (string, obrigatório): Tipo de Operação (ex.: "CREATE_RECORD" ou "UPDATE_RECORD")
**Nota:** Use esta função primeiro ao trabalhar com objetos personalizados para entender seu schema antes de realizar operações.
</Accordion>
</AccordionGroup>
## Exemplos de Uso
### Configuração Básica de um Agente Salesforce
```python
from crewai import Agent, Task, Crew
# Obtenha ferramentas enterprise (ferramentas Salesforce serão incluídas)
# Crie um agente com capacidades Salesforce
salesforce_agent = Agent(
role="CRM Manager",
goal="Manage customer relationships and sales processes efficiently",
backstory="An AI assistant specialized in CRM operations and sales automation.",
apps=['salesforce']
)
# Task to create a new lead
create_lead_task = Task(
description="Create a new lead for John Doe from Example Corp with email john.doe@example.com",
agent=salesforce_agent,
expected_output="Lead created successfully with lead ID"
)
# Run the task
crew = Crew(
agents=[salesforce_agent],
tasks=[create_lead_task]
)
crew.kickoff()
```
### Filtrando Ferramentas Salesforce Específicas
```python
# Obtenha apenas ferramentas Salesforce específicas
actions_list=["salesforce/create_record_lead", "salesforce/update_record_opportunity", "salesforce/search_records_contact"]
)
sales_manager = Agent(
role="Sales Manager",
goal="Manage leads and opportunities in the sales pipeline",
backstory="An experienced sales manager who handles lead qualification and opportunity management.",
apps=['salesforce']
)
# Task to manage sales pipeline
pipeline_task = Task(
description="Create a qualified lead and convert it to an opportunity with $50,000 value",
agent=sales_manager,
expected_output="Lead created and opportunity established successfully"
)
crew = Crew(
agents=[sales_manager],
tasks=[pipeline_task]
)
crew.kickoff()
```
### Gerenciamento de Contatos e Contas
```python
from crewai import Agent, Task, Crew
account_manager = Agent(
role="Account Manager",
goal="Manage customer accounts and maintain strong relationships",
backstory="An AI assistant that specializes in account management and customer relationship building.",
apps=['salesforce']
)
# Task to manage customer accounts
account_task = Task(
description="""
1. Create a new account for TechCorp Inc.
2. Add John Doe as the primary contact for this account
3. Create a follow-up task for next week to check on their project status
""",
agent=account_manager,
expected_output="Account, contact, and follow-up task created successfully"
)
crew = Crew(
agents=[account_manager],
tasks=[account_task]
)
crew.kickoff()
```
### Consultas SOQL Avançadas e Relatórios
```python
from crewai import Agent, Task, Crew
data_analyst = Agent(
role="Sales Data Analyst",
goal="Generate insights from Salesforce data using SOQL queries",
backstory="An analytical AI that excels at extracting meaningful insights from CRM data.",
apps=['salesforce']
)
# Complex task involving SOQL queries and data analysis
analysis_task = Task(
description="""
1. Execute a SOQL query to find all opportunities closing this quarter
2. Search for contacts at companies with opportunities over $100K
3. Create a summary report of the sales pipeline status
4. Update high-value opportunities with next steps
""",
agent=data_analyst,
expected_output="Comprehensive sales pipeline analysis with actionable insights"
)
crew = Crew(
agents=[data_analyst],
tasks=[analysis_task]
)
crew.kickoff()
```
Esta documentação abrangente cobre todas as ferramentas Salesforce organizadas por funcionalidade, facilitando que os usuários encontrem as operações específicas de que necessitam para automação de seu CRM.
### Precisa de ajuda?
<Card title="Precisa de ajuda?" icon="headset" href="mailto:support@crewai.com">
Entre em contato com nossa equipe de suporte para assistência na configuração da integração com Salesforce ou para resolução de problemas.
</Card>
Reference in New Issue View Git Blame Copy Permalink