Choose the data and destination
Set up a connection, map fields to the receiving system and filter which records qualify. An execution user determines which records and fields the integration may export.
Sales Automation and Service Console share accounts, contacts and a common set of controls. Guide people through decisions, automate routine actions and connect your business systems with the customer context and permissions already in your workspace.
Configure your data, guide your teams and connect the systems they use. Guided Processes are included in every workspace; access to app features and usage allowances follows your selected plan.
Add custom fields, organize forms and tailor saved list views. Make common layout and field changes through Setup without a code release, within the controls supported by each app.
Track business information beyond standard CRM records. Create custom objects and forms, then organize apps, tabs and home pages for your teams.
Control who can view and change objects, fields and individual records. Reusable permission bundles, team access and sharing rules support different responsibilities across the organization.
Build visual steps, decisions and business actions. Launch a guide for a user or run automation when records change or a scheduled date arrives.
See how Processes workConfigure connections, choose the data to send and map it to the receiving system. Track delivery, retries and business acknowledgements in one place.
See integration controlsBuild saved reports and dashboards from supported CRM data. Use filters and shared views to help teams track their work, with access governed by workspace permissions.
Put the questions, decisions and actions for a business process on a visual canvas. Help a person complete the work, or let a configured trigger start it.
Illustrative flow. Your administrator configures the steps, approval rules and connection.
Included in every workspace. No separate automation license or limit on active Process definitions. Record capacity, execution limits, delivery allowances and access to the underlying app features still apply.
Send CRM data to configured HTTPS endpoints for finance, fulfilment or other business systems. Decide what leaves your workspace and monitor what happens next.
Set up a connection, map fields to the receiving system and filter which records qualify. An execution user determines which records and fields the integration may export.
React to supported record events or send from a Process action. Delivery starts after the CRM change is saved; a failed save does not send its queued message.
Review delivery history and failures, retry eligible messages and handle acknowledgements. When configured, distinguish a delivered message from a handoff the receiving system accepted.
Send mapped order data to your ERP endpoint. Record the returned external reference and acceptance status so your team can follow the handoff from CRM-G.
Connections require setup and a compatible receiving endpoint; connector work may be needed. Delivery allowances vary by plan. CSV imports support additional data exchange; contact us about API access.
With sandbox features enabled, evaluate changes in a separate workspace and promote supported configuration through your release stages.
Test fields, layouts and Process definitions away from your production workspace. Choose configuration-only, sample or masked data copies, with outbound email and webhooks suppressed by default.
Package supported configuration, compare it with the destination and validate before applying it. Identify conflicts and changes made directly in the destination before release.
Promote tested releases through configured stages. Production approval policies support a separate reviewer, while deployment history records the release, decisions and outcome.
Release packages move supported configuration, not business records or credentials. Execution users, credentials and integration destinations are configured separately in each workspace.
Your organization has its own workspace address, users and configuration, with database-enforced tenant isolation alongside application access controls.
Sign in at your workspace address, such as acme.crmg.ai, or use the shared sign-in page
with your workspace name. Administrators manage user access and login policies.
Review recorded sign-in, administration and business events. Enable history tracking for selected fields on business records to see tracked changes and the people who made them.
Look up CRM records, review proposed changes and retrieve configured knowledge. Signed-in CRM actions enforce your permissions, with confirmation before writes. AI requires enabled access and a configured model provider.
External AI connections use configured credentials. Public knowledge chat cannot access CRM records. Explore the AI layer
The linked form requests a free 90-day trial and asks for a workspace name. After you verify your email, our team sets up the workspace. For a conversation or walkthrough first, contact us.