Source: [Original HTML page](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/)

Language: English

# Can AI work with the systems you already use?

Yes, where the system permits the required operation. We can write orders into your ERP, prepare quotes for review or route emails to the right person. First we check the version, licence and permissions, then test the result in your environment.

Stolen Orbit can use models from OpenAI, Anthropic (Claude), and Google Gemini to prepare work and write to Microsoft Outlook, Microsoft Excel, Microsoft Dynamics 365 Business Central, SAP Business One, Oracle NetSuite, Salesforce, HubSpot, Shopify, TeamSystem, and Zucchetti, where the version, licence and permissions support the required operation.

Stolen Orbit Sources checked on 4 November 2026

## Can you work with TeamSystem?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#teamsystem)

We can prepare orders, quotes and invoices for TeamSystem; writing them into your ERP depends on the specific product and licence you use.

**Read the details**

TeamSystem does not identify one universal API. Its Commerce developer page concerns ecommerce. Fatture in Cloud documents API creation of invoices, quotes and orders. Neither source establishes that the same operations are available in TeamSystem Enterprise or every other ERP in the group.

In the first meeting we identify the full product name, version, enabled modules and a document you need to create. With whoever manages your contract, we check API access, permissions and conditions for external integration. We then choose an API write or an import file in a documented format. Creating an invoice and submitting it to Italy’s Sistema di Interscambio remain separate steps.

References: [TeamSystem Commerce — API per sviluppatori](https://www.teamsystem.com/commerce/funzionalita/api-sviluppatori/) · [Fatture in Cloud — Invoice creation](https://developers.fattureincloud.it/docs/guides/invoice-creation/)

## Does Zucchetti have APIs for orders and invoices?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#zucchetti)

Zucchetti documents REST APIs for MagoWeb; entering an order or invoice requires checking that the record is supported in your configuration.

**Read the details**

The Mago API page establishes an access method, but does not establish writable fields, available operations or the cost of required modules. We do not extend that claim to all Zucchetti products.

We can prepare data from emails and PDFs and write it to the intended record if access allows it. In the first meeting we identify the product, version and licence, then ask your ERP administrator for operation documentation and a test environment. If the API cannot handle the task, we assess only imports supported by that product. An “API” label alone does not prove invoice creation is available.

References: [Zucchetti — MagoWeb, Mago API](https://www.zucchetti.it/it/cms/soluzioni/software-gestionali/tecnologia/gestionali-in-cloud/magoweb/software-gestionale-cloud-configurazioni.html)

## Can you automate orders in SAP Business One?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#sap-business-one)

Yes. We can write an emailed order into SAP Business One through Service Layer when your installation exposes the required operation and access.

**Read the details**

SAP documents order creation through POST Orders. With approval procedures enabled, the request may create a draft instead. We therefore check the resulting document and its status, as well as the technical response.

In the first meeting we check the version, database, Service Layer availability, access licensing and user permissions. On a sample order we map the customer, item codes, quantities, units, warehouse and custom fields. Before launch we also test a missing item code and the same order arriving twice. SAP Business One compatibility does not establish compatibility with other SAP products.

References: [SAP Business One — Service Layer API Reference](https://help.sap.com/doc/056f69366b5345a386bb8149f1700c19/10.0/en-US/Service%20Layer%20API%20Reference.html)

## Can you write orders into Microsoft Dynamics 365 Business Central?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#business-central)

Yes. We can use Microsoft Dynamics 365 Business Central APIs to create orders from AI-prepared data, with the checks and approvals agreed for the process.

**Read the details**

Microsoft documents creation of salesOrders. AI can interpret the request; the integration must then resolve customers and items, populate the header and lines, and read the order back. Creating an order does not mean goods have shipped or an invoice has been posted.

In the first meeting we check whether you use online or on-premises deployment, the correct environment and company, enabled APIs and granted permissions. Your administrator confirms licensing and access, including fields added by extensions. The test covers lines, prices, units and final status; a field visible in the interface may need a custom API.

References: [Microsoft Learn — Create salesOrders](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/api/dynamics_salesorder_create) · [Microsoft Learn — Business Central API endpoints](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/endpoints-apis-for-dynamics)

## Can you create and update orders in Oracle NetSuite?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#netsuite)

Yes. We can use SuiteTalk REST to work with Oracle NetSuite orders, within the record types and permissions available in your account.

**Read the details**

Oracle documents record operations and the salesorder record. We can prepare an order from an incoming request and verify the write. Oracle requires SuiteTax for taxation through REST; we do not assume a legacy tax setup behaves the same way.

In the first meeting we check enabled services, access roles, licensing, relevant subsidiaries and required fields. We agree which values, such as prices and taxes, must come from NetSuite rather than AI. Testing starts with a record in an authorized environment and includes rejected lines and changes a person has already made.

References: [Oracle NetSuite — SuiteTalk REST Web Services](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_1540391670.html) · [Oracle NetSuite — Sales Order](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_159665260887.html)

## Can AI update Salesforce after an email?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#salesforce)

Yes. We can have AI prepare an update from an email and write authorized fields into Salesforce through its REST APIs.

**Read the details**

This can support an incoming sales enquiry, a deal status change or quote follow-up. Salesforce documents record creation and updates through sObject resources. The objects and fields depend on your account design; we do not assume every account handles quotes or invoices the same way.

In the first meeting we check the edition, included or additional API access, object and field permissions, and validation rules. We choose a sample enquiry, its destination record and the changes that need approval. Testing checks that an update does not overwrite a colleague’s work or restart reminders after a customer has replied.

References: [Salesforce — Create a Record](https://developer.salesforce.com/docs/platform/api-rest/guide/dome-sobject-create.html) · [Salesforce — Editions with API access](https://help.salesforce.com/s/articleView?id=000005140&language=en_US&type=1) · [Salesforce — Update a Record](https://developer.salesforce.com/docs/platform/api-rest/guide/dome-update-fields.html)

## Can you update HubSpot and follow up quotes?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#hubspot)

Yes. We can update HubSpot deals from emails and quotes through the CRM APIs and authorized fields.

**Read the details**

HubSpot documents deal creation and updates, with properties and associations to contacts and companies. We can record a reply’s outcome and prepare the next step; customer-facing sends follow the agreed rules. Updating a deal does not issue a quote or create an invoice.

In the first meeting we check the subscription, app scopes, pipeline stage IDs and custom fields. Any quote or sending features are checked separately rather than inferred from deal access. On a sample deal we test the correct contact association and stopping follow-up after a reply.

References: [HubSpot — CRM API, Deals](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/deals/guide)

## Can you prepare Shopify orders from emails or sales enquiries?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#shopify)

Yes. We can create a Shopify draft order from an incoming request using the GraphQL Admin API.

**Read the details**

Shopify documents draftOrderCreate for orders with customer details, line items and addresses. The draft allows review before completing the order. Creating it does not collect payment, ship goods or issue a statutory tax invoice.

In the first meeting we check the plan, API version, app and user permissions, and availability of the required features, including any B2B terms. A sample request lets us check variants, quantities, discounts and addresses. Preparation, confirmation and customer communication have separate authorization rules; a repeated request must not create two drafts.

References: [Shopify — draftOrderCreate](https://shopify.dev/docs/api/admin-graphql/latest/mutations/draftOrderCreate)

## Can you triage email and draft replies in Microsoft Outlook?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#outlook)

Yes. We can classify messages and prepare drafts in Microsoft Outlook through Microsoft Graph, within mailboxes you authorize us to access.

**Read the details**

Microsoft documents message-property updates and draft creation. We can distinguish orders, quote requests and support enquiries, update categories and prepare text for review. Creating a draft and sending it are separate operations.

In the first meeting we check where your mail is hosted, the subscription, shared mailboxes and required administrator consent. Having Outlook installed does not establish Graph access. The test checks the correct mailbox, categories, draft visibility and exclusion of messages outside the authorized scope.

References: [Microsoft Learn — Update message](https://learn.microsoft.com/en-us/graph/api/message-update?view=graph-rest-1.0) · [Microsoft Learn — Create message](https://learn.microsoft.com/en-us/graph/api/user-post-messages?view=graph-rest-1.0)

## Can AI write into our Microsoft Excel files?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#excel)

Yes. We can write to Microsoft Excel ranges through Microsoft Graph when the file and permissions are supported, or prepare a file for review.

**Read the details**

We can populate order lines, enquiry summaries and quote inputs while leaving agreed calculations to existing formulas. Microsoft’s Update range endpoint requires delegated permission and does not support application-only permission. We therefore do not assume an unattended process can use it with an application credential alone.

In the first meeting we inspect a sample workbook, its storage location, format, Microsoft 365 plan and edit permissions. We define writable cells, formulas to preserve and how concurrent edits are handled. A completed spreadsheet does not establish that an order also reached the ERP; that step needs its own verification.

References: [Microsoft Learn — Update range](https://learn.microsoft.com/en-us/graph/api/range-update?view=graph-rest-1.0)

## Can you connect ChatGPT to our ERP using OpenAI?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#openai)

We can build an OpenAI API connection that prepares orders and requests for writing into your ERP; using it inside ChatGPT needs a separate check.

**Read the details**

With function calling, the model proposes an operation and its inputs. The code we build checks permissions, fields and approval before calling the ERP API. The model does not acquire write access by itself, and a chat response is not confirmation that an order exists.

In the first meeting we separate the preferred interface from API access: account, plan, available models, usage costs and data handling must be checked for the chosen route. We start from a sample request and its intended final record. If the work must happen inside ChatGPT, we also check the connection features permitted by your account.

References: [OpenAI — Function calling](https://developers.openai.com/api/docs/guides/function-calling)

## Can Claude prepare an order and write it into our ERP?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#claude)

Yes. We can use Anthropic’s Claude API to prepare an order and request a write through an authorized operation.

**Read the details**

Anthropic documents tool use: for tools run by our integration, Claude returns the request and application code executes it. We can interpret an email, propose the fields and stop when an item code is missing or approval is needed. The ERP supplies the outcome, not the model’s prose.

In the first meeting we check API access, model, usage limits and data permitted for processing, alongside ERP permissions. If you want to work inside the Claude app, its plan and available connections are checked separately. Testing includes an ambiguous request and an ERP rejection; neither should be reported as a completed order.

References: [Anthropic — Tool use with Claude](https://platform.claude.com/docs/en/agents-and-tools/tool-use/overview)

## Can you use Google Gemini with the same business systems?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#gemini)

Yes. We can use Google Gemini APIs to interpret requests and prepare operations for authorized business systems.

**Read the details**

Google documents function calling to connect Gemini with external functions. We can use it to classify emails or prepare order fields; the write then goes through the destination system’s API and agreed checks. Choosing Gemini does not expose capabilities the ERP lacks.

In the first meeting we check the actual Google service, API access, model, limits, costs and data handling. The Gemini app and APIs should not be treated as interchangeable. We compare output on approved examples; switching models requires retesting the same cases even when the ERP write method stays the same.

References: [Google — Function calling with the Gemini API](https://ai.google.dev/gemini-api/docs/function-calling)

## What if our ERP has no accessible API?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#senza-api)

We can start with an import file or a draft for review when the product offers no suitable API access.

**Read the details**

A CSV or Excel file helps only if it matches the format your ERP accepts. We ask for its import documentation, required fields and error report; we do not promise a universal format. If manual entry remains necessary, we identify that before work starts.

An email can deliver information to a person, but does not prove it was recorded. Database access is considered only where documented and authorized; we do not bypass ERP rules by writing directly to its tables. In the first meeting we agree how to verify the final result, including rejected records, and who completes any remaining manual steps.

## What do you check in the first meeting?

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#primo-incontro)

We start with the exact product and one real operation: what arrives, where it must end up and who may approve it.

**Read the details**

We review a request and the record you currently prepare. With your system administrator we check version, licence, modules, documentation, fields and access. No passwords belong in the contact form. Any unanswered technical question is recorded for confirmation with your system owner.

Before committing to a write, we agree an authorized test: prepare a record, read it back and compare fields and status. We also test a duplicate and a failure. The outcome is a concrete scope: what can be written, what needs approval, what stays manual and which access is missing. Public documentation establishes that a method exists; testing establishes whether it works in your environment.

## Three approaches that can work together

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#definitions)

These categories overlap. Shopify Flow, for example, also supports connectors to other services; Microsoft describes custom connectors as a way to expose API operations. Choose around the work, rather than a product label.

**Read the details**

**Native automation**

A capability already provided by the software you use: rules, sequences, notifications or internal workflows.

**A connector platform**

A configured workflow using operations exposed by connectors. Check the individual action, not just whether the software’s logo appears.

**Custom integration**

Code or a dedicated connector for specific interfaces and rules. It needs a named maintenance owner.

References: [Shopify Help Center — Creating workflows in Shopify Flow](https://help.shopify.com/en/manual/shopify-flow/create) · [Microsoft Learn — Custom connectors overview](https://learn.microsoft.com/en-us/connectors/custom-connectors/)

## A table for the first decision

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#comparison)

**Read the details**

Scroll the table to compare all columns.

Evaluation criteria, not a product ranking

| Question | Native capability | Connectors | Custom integration |
| --- | --- | --- | --- |
| When to consider it | The software already supports the task and has the required data. | The task crosses tools and the necessary operations are exposed. | An operation is missing, or other approaches cannot adequately express a required rule. |
| What to verify | Exact event, fields, conditions, exclusions and features in the actual plan. | Exact action, authentication, limits, update frequency and error handling. | Supported API or import, permissions, data schema and confirmation of the result. |
| A limit to recognise | An internal rule may not see a reply or update received by another system. | A connector may expose only some of the software’s operations. | Custom code does not remove the destination system’s limits or access requirements. |
| Who keeps it working | An owner familiar with the software, rules and notifications. | A workflow owner who checks connections, failures and application changes. | A technical owner for code, access, monitoring and updates. |
| How to assess the commitment | Configuration, testing, required plan and rule reviews. | Configuration, platform usage, testing and connection maintenance. | Design, development, infrastructure, testing and ongoing maintenance. |
| What to receive at handover | Documented rules, tests and instructions for pausing the workflow. | A connection map, account ownership and failure procedure. | Agreed code and configuration, documentation, tests and a recovery procedure. |

## Three cases to orient the decision

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#three-cases)

**Read the details**

1.  ### A reminder within the CRM
    
    Check native capabilities first if the CRM knows the quote, reply and current status. If replies arrive elsewhere and are not recorded, connect that information or keep the reminder internal.
    
2.  ### An order must update another tool
    
    Check whether a connector exposes the exact event, fields and action required. Test a repeated event and a temporarily unavailable destination too.
    
3.  ### A business system accepts a specific file format
    
    Check its documented import before choosing a dedicated integration. A custom transformation may be enough; automatic writing is not essential to the first project.
    

## A practical test tells you more than a demo

[Source for this section](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/#proof)

Shopify’s documentation illustrates why the exact event matters: different order events expose different data. Microsoft documents explicit failure and timeout paths. That is why a practical test should cover exceptions and recovery as well as a successful run.

**Read the details**

-   Show an authorised real example from its source through to the destination result.
-   Check a missing field and a case requiring approval.
-   Repeat the same event without creating a duplicate.
-   Simulate failure and show who sees it, what stays pending and how work resumes.
-   Check account ownership, which data moves and how access can be revoked.
-   Agree how to pause the workflow without losing outstanding work.

References: [Shopify Help Center — Understanding triggers in Shopify Flow](https://help.shopify.com/en/manual/shopify-flow/getting-started/understanding-triggers) · [Microsoft Learn — Employ robust error handling](https://learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/error-handling)

## Practical questions

**Can you work with TeamSystem?**

We can prepare the data; writing it requires checking the product, version, licence and operation. Fatture in Cloud or TeamSystem Commerce APIs do not establish access to every TeamSystem ERP.

**Can you write orders into Business Central?**

Yes, through Microsoft Dynamics 365 Business Central APIs when the environment and permissions allow it. We verify the customer, lines, required fields and approvals, then read the order back to confirm the result.

**Is a ChatGPT or Claude subscription enough to connect our ERP?**

No. ERP access and the chosen route must be checked: a connection inside the app or API-based integration. Plans, permissions, costs and write controls depend on that route.

**Does an available connector guarantee compatibility?**

No. Verify the operation, fields, plan, permissions and actual version or configuration. Compatibility has to be demonstrated for the required process.

**Is custom integration always better value?**

No. Compare the full commitment, including testing, usage, support and future changes. If an existing capability correctly handles the task, it may be the simplest starting point.

**Do we have to choose just one approach?**

No. A native rule can start the work, a connection can move the data, and a small custom step can transform it. Each part needs a clear purpose and owner.

## Sources

-   [Shopify Help Center — Creating workflows in Shopify Flow](https://help.shopify.com/en/manual/shopify-flow/create)
-   [Shopify Help Center — Understanding triggers in Shopify Flow](https://help.shopify.com/en/manual/shopify-flow/getting-started/understanding-triggers)
-   [Microsoft Learn — Custom connectors overview](https://learn.microsoft.com/en-us/connectors/custom-connectors/)
-   [Microsoft Learn — Employ robust error handling](https://learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/error-handling)
-   [TeamSystem Commerce — API per sviluppatori](https://www.teamsystem.com/commerce/funzionalita/api-sviluppatori/)
-   [Fatture in Cloud — Invoice creation](https://developers.fattureincloud.it/docs/guides/invoice-creation/)
-   [Zucchetti — MagoWeb, Mago API](https://www.zucchetti.it/it/cms/soluzioni/software-gestionali/tecnologia/gestionali-in-cloud/magoweb/software-gestionale-cloud-configurazioni.html)
-   [SAP Business One — Service Layer API Reference](https://help.sap.com/doc/056f69366b5345a386bb8149f1700c19/10.0/en-US/Service%20Layer%20API%20Reference.html)
-   [Microsoft Learn — Create salesOrders](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/api/dynamics_salesorder_create)
-   [Microsoft Learn — Business Central API endpoints](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/api-reference/v2.0/endpoints-apis-for-dynamics)
-   [Oracle NetSuite — SuiteTalk REST Web Services](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_1540391670.html)
-   [Oracle NetSuite — Sales Order](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_159665260887.html)
-   [Salesforce — Create a Record](https://developer.salesforce.com/docs/platform/api-rest/guide/dome-sobject-create.html)
-   [Salesforce — Editions with API access](https://help.salesforce.com/s/articleView?id=000005140&language=en_US&type=1)
-   [HubSpot — CRM API, Deals](https://developers.hubspot.com/docs/api-reference/legacy/crm/objects/deals/guide)
-   [Shopify — draftOrderCreate](https://shopify.dev/docs/api/admin-graphql/latest/mutations/draftOrderCreate)
-   [Microsoft Learn — Update message](https://learn.microsoft.com/en-us/graph/api/message-update?view=graph-rest-1.0)
-   [Microsoft Learn — Create message](https://learn.microsoft.com/en-us/graph/api/user-post-messages?view=graph-rest-1.0)
-   [Microsoft Learn — Update range](https://learn.microsoft.com/en-us/graph/api/range-update?view=graph-rest-1.0)
-   [OpenAI — Function calling](https://developers.openai.com/api/docs/guides/function-calling)
-   [Anthropic — Tool use with Claude](https://platform.claude.com/docs/en/agents-and-tools/tool-use/overview)
-   [Google — Function calling with the Gemini API](https://ai.google.dev/gemini-api/docs/function-calling)
-   [Salesforce — Update a Record](https://developer.salesforce.com/docs/platform/api-rest/guide/dome-update-fields.html)

[The email order checklist](https://stolenorbit.com/en/resources/email-order-preparation-guide/)

[Quote follow-up rules](https://stolenorbit.com/en/resources/quote-follow-up-guide/)

[Writing to your ERP: how we work](https://stolenorbit.com/en/services/erp-integration-automation/)

[Your company’s own AI](https://stolenorbit.com/en/services/company-ai-assistant/)

[What “We work with” means](https://stolenorbit.com/en/legal/#trademarks)

## Let’s start with your case.

[Let’s assess your case](https://stolenorbit.com/en/contact/)

## Turn the question into a next step.

-   [Automation failures and duplicates](https://stolenorbit.com/en/resources/automation-failures-and-duplicates/)
-   [System integration map](https://stolenorbit.com/en/templates/integration-map/)
-   [ERP integration](https://stolenorbit.com/en/services/erp-integration-automation/)
