1. CRM Connectors

These CRM connectors enable your workflow to seamlessly integrate with popular Customer Relationship Management platforms, allowing data extraction, transformation, and synchronization for your RAG applications.

1.1 Salesforce

Salesforce Connector Interface

Description

The Salesforce connector enables seamless integration with Salesforce CRM, allowing you to extract data using SOQL (Salesforce Object Query Language) queries. This connector provides read access to your Salesforce instance, empowering you to retrieve customer data, sales information, and other business-critical records.

Use Cases

Retrieving customer records to enhance AI-powered sales assistants
Extracting opportunity data for sales forecasting and analysis
Accessing lead information for personalized marketing campaigns
Integrating case data for improved customer support experiences
Building custom dashboards with real-time Salesforce data

Inputs

Salesforce Username: Your Salesforce account username (required)
Example: user@example.com
Salesforce Password: Your Salesforce account password (required)
Example: ••••••••
Salesforce Security Token: Security token for API access (required)
Example: a1B2c3D4e5F6g7H8i9J0
SOQL Queries: Salesforce Object Query Language statements (required)
Example: SELECT Id, Name, Email, Phone FROM Contact WHERE LastModifiedDate > LAST_WEEK

Outputs

The connector returns Salesforce records matching your SOQL query in JSON format.

Example Output:

{
  "totalSize": 2,
  "done": true,
  "records": [
    {
      "Id": "0031s00000A2azdAAB",
      "Name": "John Doe",
      "Email": "john.doe@example.com",
      "Phone": "555-123-4567",
      "attributes": {
        "type": "Contact",
        "url": "/services/data/v55.0/sobjects/Contact/0031s00000A2azdAAB"
      }
    },
    {
      "Id": "0031s00000BxTr9AAF",
      "Name": "Jane Smith",
      "Email": "jane.smith@example.com",
      "Phone": "555-987-6543",
      "attributes": {
        "type": "Contact",
        "url": "/services/data/v55.0/sobjects/Contact/0031s00000BxTr9AAF"
      }
    }
  ]
}

Implementation Notes

Optimize SOQL queries with appropriate WHERE clauses to minimize data transfer and processing time
Use LIMIT in your queries to control the number of records returned
Include only necessary fields in your SELECT statements to improve performance
Be mindful of API limits in your Salesforce organization
Consider using Connected Apps and OAuth for enhanced security in production environments

1.2 Salesforce Insert

Salesforce Insert Connector Interface

Description

The Salesforce Insert connector allows you to create or update records in your Salesforce CRM instance. This connector serves as a bridge for writing data into Salesforce, enabling automated record creation based on workflow outputs, user interactions, or other system integrations.

Use Cases

Creating leads automatically from website form submissions
Adding contacts captured through conversational interfaces
Generating opportunities based on predictive analytics
Creating cases from customer support interactions
Updating existing records with enriched information

Inputs

Salesforce Username: Your Salesforce account username (required)
Example: user@example.com
Salesforce Password: Your Salesforce account password (required)
Example: ••••••••
Security Token: Salesforce security token for API access (required)
Example: a1B2c3D4e5F6g7H8i9J0
Object Salesforce: The Salesforce object type to create or update (required)
Example: Lead, Contact, Opportunity, Case
JSON data of the record: JSON representation of the record to insert (required)
Example: {"FirstName": "John", "LastName": "Smith", "Email": "john.smith@example.com", "Company": "Acme Inc"}

Outputs

The connector returns the result of the insert operation, including success status and record ID.

Example Output:

{
  "success": true,
  "id": "00Q3t00001X1xp9EAB",
  "errors": [],
  "created": true,
  "message": "Record successfully created"
}

Implementation Notes

Ensure all required fields for the Salesforce object are included in your JSON data
Use external ID fields for upsert operations to avoid creating duplicate records
Implement validation logic before insertion to ensure data quality
For bulk operations, consider using batch processing to optimize API usage
Monitor API limits to avoid hitting Salesforce's daily API request limits

1.3 Odoo Insert Lead

Odoo Insert Lead Connector Interface

Description

The Odoo Insert Lead connector enables you to create new leads directly in your Odoo CRM system. This connector streamlines the process of capturing potential customer information from various sources and automatically importing it into your Odoo sales pipeline for follow-up by your sales team.

Use Cases

Capturing leads from website forms and landing pages
Creating leads from marketing campaign responses
Converting social media inquiries into sales opportunities
Generating leads from trade shows and events
Automating lead creation from email interactions

Inputs

Lead data (JSON): JSON object containing lead information (required)
Example: {"name": "John Smith", "email": "john.smith@example.com", "phone": "555-123-4567"}
Odoo database name: The name of your Odoo database (required)
Example: mycompany
Password (or API Key): Authentication credential for Odoo (required)
Example: api_key_12345abcdef
Odoo server URL: URL of your Odoo server instance (required)
Example: https://mycompany.odoo.com
Username: Odoo user account username (required)
Example: admin@mycompany.com

Outputs

The connector returns the result of the lead creation operation, including the newly created lead ID and status information.

Example Output:

{
  "success": true,
  "lead_id": 42,
  "message": "Lead successfully created",
  "status": "New",
  "created_date": "2023-09-15 14:32:45"
}

Implementation Notes

Map lead fields correctly according to your Odoo configuration
Implement deduplication logic to avoid creating duplicate leads
Consider using Odoo's External ID system for reliable data synchronization
Use proper error handling to manage API connectivity issues
Ensure the API user has sufficient permissions to create leads in Odoo

1.4 Odoo Insert Contact

Odoo Insert Contact Connector Interface

Description

The Odoo Insert Contact connector facilitates the creation of new contacts in your Odoo CRM system. This connector streamlines the process of adding individuals and organizations to your contact database, enabling effective relationship management and communication with customers, suppliers, and partners.

Use Cases

Creating customer contacts from web forms or sign-up processes
Adding supplier contact information to your database
Converting leads into contacts after qualification
Importing business card information from networking events
Maintaining up-to-date contact information from multiple channels

Inputs

contact data (JSON): JSON object containing contact information (required)
Example: {"name": "Sarah Johnson", "email": "sarah.johnson@example.com", "phone": "555-987-6543", "company_name": "TechSolutions Inc"}
Odoo database name: The name of your Odoo database (required)
Example: mycompany
Password (or API Key): Authentication credential for Odoo (required)
Example: api_key_67890uvwxyz
Odoo server URL: URL of your Odoo server instance (required)
Example: https://mycompany.odoo.com
Username: Odoo user account username (required)
Example: admin@mycompany.com

Outputs

The connector returns the result of the contact creation operation, including the newly created contact ID and status information.

Example Output:

{
  "success": true,
  "contact_id": 247,
  "message": "Contact successfully created",
  "is_company": false,
  "created_date": "2023-09-16 09:45:12"
}

Implementation Notes

Distinguish between individual and company contacts using appropriate fields
Implement contact validation to ensure data quality (email format, phone numbers)
Use Odoo's hierarchy features to properly link contacts with parent companies
Consider address formatting according to country-specific standards
Handle duplicate detection to maintain a clean contact database

1.5 Odoo CRM Read

Odoo CRM Read Connector Interface

Description

The Odoo CRM Read connector allows you to retrieve and query data from your Odoo CRM system. This connector provides read access to various CRM objects like leads, opportunities, contacts, and sales orders, enabling you to incorporate existing Odoo data into your workflows and applications.

Use Cases

Retrieving customer information for personalized communications
Accessing lead data for sales analysis and forecasting
Extracting opportunity information for pipeline visualization
Querying sales order data for revenue reporting
Retrieving contact details for data enrichment processes

Inputs

Filter domains (JSON List): Domain filter expressions to query specific records (required)
Example: [["name", "ilike", "Tech"], ["create_date", >=: 2023-01-01]]
Limit de résultats: Maximum number of records to return (optional)
Example: 10
Nom de la base Odoo: The name of your Odoo database (required)
Example: mycompany
Mot de passe (ou API Key): Authentication credential for Odoo (required)
Example: api_key_12345abcdef
URL du serveur Odoo: URL of your Odoo server instance (required)
Example: https://mycompany.odoo.com
Nom d'utilisateur: Odoo user account username (required)
Example: admin@mycompany.com
Type de ressource: Odoo model/object type to query (required)
Example: crm.lead, res.partner, sale.order

Outputs

The connector returns the query results containing the requested Odoo CRM records in JSON format.

Example Output:

{
  "results": [
    {
      "id": 124,
      "name": "TechCorp Server Upgrade",
      "partner_id": [352, "TechCorp"],
      "email": "contact@techcorp.com",
      "phone": "555-789-1234",
      "stage_id": [3, "Qualified"],
      "probability": 65,
      "expected_revenue": 25000,
      "create_date": "2023-05-12 09:25:33"
    },
    {
      "id": 125,
      "name": "TechSolutions Software Implementation",
      "partner_id": [298, "TechSolutions Inc"],
      "email": "projects@techsolutions.com",
      "phone": "555-456-7890",
      "stage_id": [4, "Proposition"],
      "probability": 80,
      "expected_revenue": 48000,
      "create_date": "2023-05-15 14:18:22"
    }
  ],
  "total_count": 2,
  "limit": 10,
  "status": "success"
}

Implementation Notes

Use efficient domain filters to limit data retrieval and improve performance
Understand Odoo's domain filter syntax for effective querying
Consider paginating results for large data sets by using limit and offset
Monitor API usage to stay within Odoo's performance boundaries
Cache frequently accessed data to reduce API calls when appropriate

1.6 Zoho CRM Insert

Zoho CRM Insert Connector Interface

Description

The Zoho CRM Insert connector enables you to create new records in your Zoho CRM system. This connector serves as a powerful integration point for adding leads, contacts, accounts, deals, and other CRM entities directly from your workflows, automating data entry and ensuring consistency across your business systems.

Use Cases

Creating new leads from website form submissions or landing pages
Adding contacts from email interactions or business networking events
Generating deals based on customer inquiries or sales interactions
Creating tasks for follow-up actions triggered by workflow events
Adding notes to customer records for comprehensive activity logging

Inputs

Client ID: Your Zoho API client ID (required)
Example: 1000.ABCDEFG123456789
Client Secret: Your Zoho API client secret (required)
Example: 1234567890abcdefghijklm
Refresh Token: Long-lived refresh token for authentication (required)
Example: 1000.12345abcde.67890fghij
Zoho API Domain: The regional API domain for your Zoho account (required)
Example: https://accounts.zoho.com
Module CRM: The Zoho CRM module where the record will be created (required)
Example: Leads, Contacts, Accounts, Deals
Data of the new record: (JSON Object) JSON representation of the record to insert (required)
Example: {"Last_Name": "Doe", "Email": "doe@example.com", "Company": "ABC Corp", "Phone": "555-123-4567"}

Outputs

The connector returns the result of the insert operation, including success status and the newly created record ID.

Example Output:

{
  "status": "success",
  "message": "Record added successfully",
  "data": {
    "id": "3286534000000458001",
    "created_time": "2023-08-22T15:28:34-0700",
    "module": "Leads",
    "status_code": 201
  },
  "details": {
    "Modified_Time": "2023-08-22T15:28:34-0700",
    "Modified_By": {
      "id": "3286534000000235001",
      "name": "John Admin"
    },
    "Created_Time": "2023-08-22T15:28:34-0700",
    "id": "3286534000000458001"
  }
}

Implementation Notes

Ensure all required fields for the selected Zoho module are included in your data
Use proper field naming conventions as defined in your Zoho CRM setup
Implement token refresh mechanism to maintain authentication
Consider using bulk insert for multiple records to optimize API usage
Handle field validation before insertion to ensure data quality

1.7 Zoho CRM Reader

Zoho CRM Reader Connector Interface

Description

The Zoho CRM Reader connector allows you to retrieve and query data from your Zoho CRM platform. This connector provides read access to various modules like leads, contacts, accounts, deals, and more, enabling you to integrate existing Zoho CRM data into your workflows and applications.

Use Cases

Retrieving lead information for sales intelligence applications
Accessing contact data for personalized marketing campaigns
Extracting account details for account-based strategies
Querying deal information for revenue forecasting
Integrating task and activity data for workflow automation

Inputs

Client ID: Your Zoho API client ID (required)
Example: 1000.ABCDEFG123456789
Client Secret: Your Zoho API client secret (required)
Example: 1234567890abcdefghijklm
Refresh Token: Long-lived refresh token for authentication (required)
Example: 1000.12345abcde.67890fghij
Zoho API Domain: The regional API domain for your Zoho account (required)
Example: https://accounts.zoho.com
Module CRM: The Zoho CRM module to query (required)
Example: Leads, Contacts, Accounts, Deals
Query Criteria: Filter conditions for the query (optional)
Example: (Email:equals:example@email.com)

Outputs

The connector returns the Zoho CRM records matching your query criteria in JSON format.

Example Output:

{
  "status": "success",
  "data": [
    {
      "id": "4782934000000361001",
      "Owner": {
        "id": "4782934000000147001",
        "name": "Alex Rodriguez"
      },
      "Email": "michael.brown@example.com",
      "First_Name": "Michael",
      "Last_Name": "Brown",
      "Company": "Global Tech Solutions",
      "Phone": "555-234-5678",
      "Lead_Status": "Qualified",
      "Created_Time": "2023-07-12T14:25:36-0700",
      "Modified_Time": "2023-08-03T09:18:42-0700",
      "Lead_Source": "Website"
    },
    {
      "id": "4782934000000375009",
      "Owner": {
        "id": "4782934000000147001",
        "name": "Alex Rodriguez"
      },
      "Email": "laura.wilson@example.com",
      "First_Name": "Laura",
      "Last_Name": "Wilson",
      "Company": "Innovative Systems Inc.",
      "Phone": "555-876-5432",
      "Lead_Status": "Contacted",
      "Created_Time": "2023-07-15T10:42:18-0700",
      "Modified_Time": "2023-07-25T16:35:27-0700",
      "Lead_Source": "Referral"
    }
  ],
  "info": {
    "more_records": false,
    "count": 2,
    "page": 1,
    "per_page": 200
  }
}

Implementation Notes

Use efficient query criteria to limit data retrieval and improve performance
Implement token refresh mechanism to maintain authentication
Consider pagination for handling large result sets
Be mindful of API rate limits based on your Zoho subscription
Use field selection to retrieve only necessary data fields

1.8 HubSpot Read

HubSpot Read Connector Interface

Description

The HubSpot Read connector enables you to retrieve and query data from your HubSpot CRM platform. This connector provides read access to contacts, companies, deals, tickets, and other HubSpot objects, allowing you to integrate HubSpot data into your workflows and applications for enhanced customer insights and engagement.

Use Cases

Accessing contact data for personalized marketing campaigns
Retrieving company information for account-based strategies
Extracting deal data for sales forecasting and analysis
Querying ticket information for customer support enhancements
Pulling engagement data for customer interaction analysis

Inputs

Access Token: Your HubSpot API access token (required)
Example: pat-na1-12345678-abcd-efgh-ijkl-1234567890ab
CRM Object: The HubSpot object type to query (required)
Example: contacts, companies, deals, tickets
property name: Specific property fields to filter by (optional)
Example: email, firstname, lastname, phone
filter Operation: Filter operation for property queries (optional)
Example: EQ (equals), GT (greater than), LT (less than)
Filter value: Value to filter properties by (optional)
Example: "example@email.com", "2023-01-01"
Maximum number of results: Limit on number of records to return (optional)
Example: 10

Outputs

The connector returns the HubSpot records matching your query criteria in JSON format.

Example Output:

{
  "results": [
    {
      "id": "12345",
      "properties": {
        "createdate": "2023-04-15T14:32:23.867Z",
        "email": "john.smith@example.com",
        "firstname": "John",
        "lastname": "Smith",
        "phone": "+1 (555) 123-4567",
        "company": "Example Corp",
        "lifecyclestage": "lead",
        "hs_lead_status": "NEW"
      },
      "createdAt": "2023-04-15T14:32:23.867Z",
      "updatedAt": "2023-05-22T09:18:45.123Z",
      "archived": false
    },
    {
      "id": "67890",
      "properties": {
        "createdate": "2023-04-18T10:27:56.432Z",
        "email": "jane.doe@example.com",
        "firstname": "Jane",
        "lastname": "Doe",
        "phone": "+1 (555) 987-6543",
        "company": "Sample Inc",
        "lifecyclestage": "marketingqualifiedlead",
        "hs_lead_status": "OPEN"
      },
      "createdAt": "2023-04-18T10:27:56.432Z",
      "updatedAt": "2023-05-24T15:42:18.765Z",
      "archived": false
    }
  ],
  "paging": {
    "next": {
      "after": "67890",
      "link": "https://api.hubapi.com/crm/v3/objects/contacts?after=67890&limit=10"
    }
  },
  "total": 2
}

Implementation Notes

Specify only the properties you need to optimize API performance
Use appropriate filter operations to narrow down results effectively
Implement pagination handling for large data sets using the paging information
Be mindful of HubSpot's API rate limits (depends on your subscription)
Consider using Private Apps with scoped access for enhanced security

1.9 HubSpot Insert

HubSpot Insert Connector Interface

Description

The HubSpot Insert connector allows you to create or update records in your HubSpot CRM platform. This connector streamlines the process of adding contacts, companies, deals, tickets, and other objects to your HubSpot database, enabling automated data entry from various sources and ensuring your CRM stays up-to-date with the latest customer information.

Use Cases

Creating contacts from form submissions or lead generation activities
Adding companies from business directory integrations
Generating deals from e-commerce purchases or quote requests
Creating tickets from customer support interactions
Updating existing records with enriched information from external sources

Inputs

Access Token: Your HubSpot API access token (required)
Example: pat-na1-12345678-abcd-efgh-ijkl-1234567890ab
CRM Object to Insert: The HubSpot object type to create (required)
Example: contacts, companies, deals, tickets
JSON data of the record: Properties of the record to create (required)
Example: {"properties": {"firstname": "Jane", "lastname": "Smith", "email": "jane.smith@example.com", "phone": "555-987-6543"}}

Outputs

The connector returns the result of the insert operation, including the newly created or updated record information.

Example Output:

{
  "id": "12345678",
  "properties": {
    "createdate": "2023-09-05T10:30:15.123Z",
    "email": "jane.smith@example.com",
    "firstname": "Jane",
    "hs_object_id": "12345678",
    "lastname": "Smith",
    "phone": "555-987-6543"
  },
  "createdAt": "2023-09-05T10:30:15.123Z",
  "updatedAt": "2023-09-05T10:30:15.123Z",
  "archived": false,
  "status": "success",
  "message": "Record successfully created"
}

Implementation Notes

Include all required properties for the HubSpot object type you're creating
Implement deduplication strategies using unique identifiers like email
Use batch APIs for inserting multiple records to optimize performance
Consider implementing webhook listeners for two-way synchronization
Validate data formats before insertion to ensure data quality

1.10 Dynamics CRM Create

Dynamics CRM Create Connector Interface

Description

The Dynamics CRM Create connector enables you to create new records in your Microsoft Dynamics 365 CRM system. This connector streamlines the process of adding entities such as leads, contacts, accounts, opportunities, and cases to your Dynamics CRM instance, allowing automated record creation from various sources and integrations.

Use Cases

Creating leads from website forms and marketing campaigns
Adding contacts from external databases or networking events
Generating opportunities from sales activities or prospect inquiries
Creating cases from customer support interactions
Adding accounts from business partner networks or industry directories

Inputs

Tenant ID: Your Microsoft Dynamics 365 tenant identifier (required)
Example: 12345678-1234-1234-1234-123456789012
Client ID: Application (client) ID from Azure AD registration (required)
Example: 87654321-4321-4321-4321-210987654321
Client Secret: Secret key for your Azure AD application (required)
Example: pAs5w0rd~C1i3nT~s3Cr3T
Dynamics Entity: The Dynamics CRM entity type to create (required)
Example: lead, contact, account, opportunity, incident
Dataverse URL: URL of your Dynamics 365 Dataverse environment (required)
Example: https://myorganization.crm.dynamics.com
Record Data (JSON): JSON representation of the record to create (required)
Example: {"firstname": "John", "lastname": "Smith", "emailaddress1": "john.smith@example.com", "telephone1": "555-123-4567", "jobtitle": "IT Director"}

Outputs

The connector returns the result of the create operation, including the newly created record ID and status information.

Example Output:

{
  "status": "success",
  "entityId": "5d8b2c67-ef14-ee11-bdf3-000d3a991234",
  "entityName": "contact",
  "createdOn": "2023-09-18T11:23:45Z",
  "message": "Record successfully created",
  "additionalDetails": {
    "oDataEtag": "W/\"91245678\"",
    "formattedEntityId": "5d8b2c67-ef14-ee11-bdf3-000d3a991234"
  }
}

Implementation Notes

Ensure all required fields for the Dynamics entity are included in your JSON data
Use proper field naming conventions as defined in your Dynamics CRM schema
Implement validation logic to ensure data quality before insertion
Consider entity relationships when creating related records
Utilize batch operations for creating multiple records efficiently

1.11 Dynamics CRM Reader

Dynamics CRM Reader Connector Interface

Description

The Dynamics CRM Reader connector provides access to retrieve and query data from your Microsoft Dynamics 365 CRM system. This connector enables you to access various entity types such as leads, contacts, accounts, opportunities, and cases, allowing you to integrate Dynamics CRM data into your workflows and applications.

Use Cases

Retrieving customer information for personalized communications
Accessing lead data for sales intelligence and follow-up automation
Extracting opportunity information for pipeline analysis and forecasting
Querying case data for customer support optimization
Integrating account details for account-based marketing strategies

Inputs

Tenant ID: Your Microsoft Dynamics 365 tenant identifier (required)
Example: 12345678-1234-1234-1234-123456789012
Client ID: Application (client) ID from Azure AD registration (required)
Example: 87654321-4321-4321-4321-210987654321
Client Secret: Secret key for your Azure AD application (required)
Example: pAs5w0rd~C1i3nT~s3Cr3T
Dynamics Entity: The Dynamics CRM entity type to query (required)
Example: lead, contact, account, opportunity, incident
Dataverse URL: URL of your Dynamics 365 Dataverse environment (required)
Example: https://myorganization.crm.dynamics.com
FetchXML or OData Query: Query expression to filter records (optional)
Example: $filter=createdon ge 2023-01-01 and statecode eq 0&$select=contactid,fullname,emailaddress1

Outputs

The connector returns the Dynamics CRM records matching your query criteria in JSON format.

Example Output:

{
  "value": [
    {
      "@odata.etag": "W/\"90765432\"",
      "contactid": "5d7a3b45-cd92-ed11-aad1-000d3a9c0234",
      "fullname": "John Smith",
      "jobtitle": "Director of Operations",
      "emailaddress1": "john.smith@example.com",
      "telephone1": "555-123-4567",
      "createdon": "2023-05-18T09:42:12Z",
      "statecode": 0,
      "address1_city": "Seattle",
      "address1_stateorprovince": "WA"
    },
    {
      "@odata.etag": "W/\"90766789\"",
      "contactid": "6c8b4c56-de03-ee11-aad1-000d3a9c8765",
      "fullname": "Sarah Johnson",
      "jobtitle": "Chief Technology Officer",
      "emailaddress1": "sarah.johnson@example.com",
      "telephone1": "555-987-6543",
      "createdon": "2023-06-22T11:15:08Z",
      "statecode": 0,
      "address1_city": "Portland",
      "address1_stateorprovince": "OR"
    }
  ],
  "@odata.context": "https://myorganization.api.crm.dynamics.com/api/data/v9.2/$metadata#contacts",
  "@Microsoft.Dynamics.CRM.totalrecordcount": 2,
  "@Microsoft.Dynamics.CRM.totalrecordcountlimitexceeded": false
}

Implementation Notes

Use OData query options ($select, $filter, $expand) to optimize data retrieval
Consider FetchXML for more complex queries with multiple relationships
Implement pagination for large result sets using $top and $skip
Be mindful of API limits and performance implications
Use appropriate authentication scopes for the specific data you're accessing

1.12 Dynamics CRM

Dynamics CRM Connector Interface

Description

The Dynamics CRM connector provides advanced data access and manipulation capabilities with Microsoft Dynamics 365. This connector facilitates custom queries, data extraction, and advanced operations beyond basic read and write functionality, enabling sophisticated integrations with your Dynamics CRM environment for specialized business requirements and complex data operations.

Use Cases

Executing advanced queries with relational data across multiple entities
Performing custom filtering and aggregation operations
Accessing specialized entity relationships and navigation properties
Running complex calculated field operations and business logic
Building comprehensive dashboards with multi-entity data sources

Inputs

Tenant ID: Your Microsoft Dynamics 365 tenant identifier (required)
Example: 12345678-1234-1234-1234-123456789012
Client ID: Application (client) ID from Azure AD registration (required)
Example: 87654321-4321-4321-4321-210987654321
Client Secret: Secret key for your Azure AD application (required)
Example: pAs5w0rd~C1i3nT~s3Cr3T
Dataverse URL: URL of your Dynamics 365 Dataverse environment (required)
Example: https://myorganization.crm.dynamics.com
Query Endpoint: API endpoint or query path for your operation (required)
Example: /api/data/v9.2/contacts, /api/data/v9.2/$filter=createdon ge 2023-01-01

Outputs

The connector returns the data from Dynamics CRM based on your specified query or operation in JSON format.

Example Output:

{
  "value": [
    {
      "@odata.etag": "W/\"90765432\"",
      "contactid": "5d7a3b45-cd92-ed11-aad1-000d3a9c0234",
      "fullname": "John Smith",
      "jobtitle": "Director of Operations",
      "emailaddress1": "john.smith@example.com",
      "telephone1": "555-123-4567",
      "createdon": "2023-05-18T09:42:12Z",
      "statecode": 0,
      "address1_city": "Seattle",
      "address1_stateorprovince": "WA"
    },
    {
      "@odata.etag": "W/\"90766789\"",
      "contactid": "6c8b4c56-de03-ee11-aad1-000d3a9c8765",
      "fullname": "Sarah Johnson",
      "jobtitle": "Chief Technology Officer",
      "emailaddress1": "sarah.johnson@example.com",
      "telephone1": "555-987-6543",
      "createdon": "2023-06-22T11:15:08Z",
      "statecode": 0,
      "address1_city": "Portland",
      "address1_stateorprovince": "OR"
    }
  ],
  "@odata.context": "https://myorganization.api.crm.dynamics.com/api/data/v9.2/$metadata#contacts",
  "@Microsoft.Dynamics.CRM.totalrecordcount": 2,
  "@Microsoft.Dynamics.CRM.totalrecordcountlimitexceeded": false
}

Implementation Notes

Leverage OData syntax for powerful query capabilities
Use $select, $filter, $expand, and $orderby options to optimize queries
Consider performance implications when expanding related entities
Utilize batch operations for multiple related operations
Implement pagination for large result sets using $top and $skip

Documentation

1. CRM Connectors

1.1 Salesforce

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.2 Salesforce Insert

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.3 Odoo Insert Lead

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.4 Odoo Insert Contact

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.5 Odoo CRM Read

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.6 Zoho CRM Insert

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.7 Zoho CRM Reader

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.8 HubSpot Read

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.9 HubSpot Insert

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.10 Dynamics CRM Create

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.11 Dynamics CRM Reader

Description

Use Cases

Inputs

Outputs

Implementation Notes

1.12 Dynamics CRM

Description

Use Cases

Inputs

Outputs

Implementation Notes