Dynamics 365 Business Central
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
ERP / Business productivity · Two-way sync platform
Dynamics 365 Business Central and SendGrid integration
Plan how Dynamics 365 Business Central and SendGrid should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
Integration planning
stacksync.com Built for teams where self-serve, reliability and scale matter
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Proposed workflow
Customer sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving Dynamics 365 Business Central Customers or SendGrid Contacts needs a defined result in the other system.
Start with Dynamics 365 Business Central Customers and SendGrid Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Review records and field ownershipProposed record relationships
Records to connect
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| Dynamics 365 Business Central record | SendGrid record | Record matching | Field ownership |
|---|---|---|---|
| CustomersProposed record; confirm Stacksync object support.Customer identity assessment | ContactsDocumented record: Read: Supported. Write: Not available (read-only connector). | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Record coverage to review
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
SendGrid
Read-only connector
Record types covered in the setup guide
| Record types | Coverage and requirements |
|---|---|
| Reading: ✅ Supported. Updating this object: Not available (read-only connector). |
Connection essentials
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | Dynamics 365 Business Central | SendGrid |
|---|---|---|
| Integration interface | REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL | REST API (v3) |
| Authentication | Confirm the credentials, API plan, and permissions required for Dynamics 365 Business Central. | API key |
| Change detection | Confirm how Stacksync detects changes for this connector and the objects you need. | The saved Stacksync guide does not specify the change-detection mechanism. |
| Read access | Confirm with Stacksync | Available for supported records |
| Write access | Confirm with Stacksync | Not supported by this connector |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
- SOC 2 Type II
- ISO 27001
- HIPAA BAA
- GDPR
- CCPA
- DPF US-EU-UK-CH
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Dynamics 365 Business Central
- Integration interface
- REST API built on OData v4 (standard API v2.0), extensible with custom API pages in AL
- Authentication
- Confirm the credentials, API plan, and permissions required for Dynamics 365 Business Central.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Dynamics 365 Business Central, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Dynamics 365 Business Central and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
SendGrid
- Integration interface
- REST API (v3)
- Authentication
- API key (create in SendGrid Settings > API Keys with Custom Access / Full Access for the objects to sync; key begins with "SG")
- Change detection
- The saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
- Read access
- Available for supported records
- Write access
- Not supported by this connector
Setup requirements
- Create a SendGrid API key with the access levels needed for the selected resources.
- Confirm the Email Activity subscription and retention requirements if that resource is needed.
Limitations to check
- The Stacksync connector is documented as read-only. It does not write changes back to SendGrid.
Technical documentation
Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.
Prepare Dynamics 365 Business Central and SendGrid access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Dynamics 365 Business Central setup checklist
- Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Dynamics 365 Business Central, including read/write support, authentication, and initial-load limits.
SendGrid setup checklist
- Create a SendGrid API key with the access levels needed for the selected resources.
- Confirm the Email Activity subscription and retention requirements if that resource is needed.
Setup guides: Authorize SendGrid
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Dynamics 365 Business Central and SendGrid planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Customer identity
Customers / Contacts
Before linking Dynamics 365 Business Central Customers to SendGrid Contacts, check whether the customer is an individual or a company. Match the correct record type in each system.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Dynamics 365 Business Central
- Object support to establish
- SendGrid
- Documented record · Read: ✅ Supported. Write: Not available (read-only connector).
- Record identity
- Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
- Field ownership
- Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Fields to include
- Source customer ID
- Person/company classification
- Legal entity or business unit
- Destination identity reference
- Record dependencies
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Validation
- Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
- Recovery
- Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
References: SendGrid: Contacts documentation
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Customers / Contacts to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Stacksync managed sync
- Best fit
- Review compatibility with a Stacksync engineer using an example of the records and updates you need.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your Dynamics 365 Business Central and SendGrid record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Customers / Contacts, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Dynamics 365 Business Central and SendGrid need a transformation, approval, or action outside a direct record sync.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
- Best fit
- Consider for a one-time Dynamics 365 Business Central / SendGrid migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Customer sync test
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Customers or Contacts record needs a defined result in the other system.
- Start with Dynamics 365 Business Central Customers and SendGrid Contacts. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Link communication history with Dynamics 365 Business Central context
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A communication in SendGrid needs an association with Customers or Vendors in Dynamics 365 Business Central.
- Select the communication records from Contacts and preserve message/call and thread IDs.
- Resolve the participant-to-business-record relationship explicitly; phone number or display name alone may be ambiguous.
- Keep history replication separate from sending a message, placing a call, or changing consent. Confirm a separate authorized operation for any action.
Expected result: Repeated delivery updates the same history record; a private conversation stays private; a history replay sends no new message.
If it fails: Check source delivery state and the destination relationship before retrying. Do not resend to repair an analytical or history discrepancy.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Customers / Contacts
Test case
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Expected result
The expected customer relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated customer change
Investigate
Inspect Dynamics 365 Business Central Customers and SendGrid Contacts, their IDs, and the destination error.
Next action
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
A record type or update is unavailable
Investigate
Check the Dynamics 365 Business Central and SendGrid connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between Dynamics 365 Business Central and SendGrid
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Dynamics 365 Business Central SendGrid Direction not supported
Detect changesThis route requires read access from Dynamics 365 Business Central and write access to SendGrid; the documented connector restrictions do not permit it.
Apply updatesUse a supported direction or review a separate integration method for this requirement.
SendGrid Dynamics 365 Business Central Direction requires confirmation
Detect changesThe saved Stacksync guide does not specify the change-detection mechanism. Confirm it for the selected objects.
Apply updatesConfirm that Stacksync can create or update the records you need in Dynamics 365 Business Central.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ
Dynamics 365 Business Central and SendGrid integration FAQ
-
Explore a Dynamics 365 Business Central and SendGrid integration with a Stacksync engineer. Stacksync support for Dynamics 365 Business Central is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
-
SendGrid is read-only through Stacksync. Two-way sync is not supported through these connectors; use a supported direction or review another implementation.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Dynamics 365 Business Central account, edition, environment, and business objects the integration must access. Create a SendGrid API key with the access levels needed for the selected resources. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Customers in Dynamics 365 Business Central and Contacts in SendGrid. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Choose a method around one example record and the update your business needs. Use Customers / Contacts to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 458 integrations listed for Dynamics 365 Business Central and SendGrid.
Popular · 4 of 458
-
Dynamics 365 Business Central and ServiceNow -
Dynamics 365 Business Central and Slack -
Dynamics 365 Business Central and Agiloft -
SendGrid and DEAR Inventory
No integrations match .
Next step
Plan your integration with an engineer
Walk through your Dynamics 365 Business Central and SendGrid records, field mappings, and requirements with an integration engineer.
