Scope
This reference describes every field an administrator configures under Estimate Setup → Settings → Connections → Connect with external MIS, plus the additional-field editor that controls what estimators see in the Export to External MIS dialog. The matching JSON payload schema — property names, types, and version — is owned by the integration team and lives in the Gelato integration documentation; it is not duplicated here. Export Log entries are listed for orientation only; their detail panel is described in Why an export failed.
Connection fields (administrator)
Field | What it controls | When to change this | What depends on it |
Connection enabled | Master switch for external-MIS export. When off, the Export button is hidden on every estimate. | Turn off when retiring an integration or temporarily pausing sends. Turn on after a fresh configuration only when Test connection succeeds. | Visibility of the Export button for every estimator. Whether automatic exports fire when a trigger status is reached. |
Export destination | Picks the receiving system: External MIS or GelatoConnect One. | When migrating from one destination to the other, or when your contract gains access to GelatoConnect One. | Which credential fields render below. Whether the JSON payload follows the external-MIS or GelatoConnect One contract. |
Triggers | One or more events that initiate an export: Manual, Quote: Draft, Quote: Waiting, Quote: Won, Quote: Accepted, Quote: Rejected, Quote: Follow-up Send, Quote: Inbound Chat, Quote: Inbound Request, Quote: Waiting for Response. | When the shop's hand-off policy changes (e.g., add Quote: Won so won quotes always export). | Which estimate status changes produce a payload automatically. Whether Export is visible to estimators (visible whenever Manual is in the list). |
Destination URL | The HTTPS endpoint the MIS exposes to receive the payload. | When the MIS migrates to a new domain, when test and production endpoints differ, or when the path on the endpoint changes. | Where every payload is POSTed. Invalid URL validation fires here on save. |
Authentication method | Selects how Estimator authenticates the request: Token, OAuth, Basic, API Key, or None. | When the MIS rotates its auth scheme, or when migrating from staging credentials to production. | Which credential fields render below (token, username/password, API key header/secret). |
Authentication token | The bearer token Estimator sends with each request when auth is Token. | When the MIS rotates the token, or after any suspected credential exposure. | Whether Test connection and every real export succeed. The field shows Token not set until populated. |
Username / Password | Basic-auth credentials when auth is Basic. | When the MIS rotates the password or the integration account changes. | The Basic-auth header on every export request. |
API Key Header / API Key Secret | The request-header name and value when auth is API Key. | When the MIS changes the expected header name (rare) or rotates the secret. | The custom header on every export request. |
Test connection | Sends a probe request to the Destination URL with the configured credentials and shows Test success or Test failure. | Run after every change to URL, method, or credential. Run before saving the connection live. | Whether you can trust the configuration before estimators rely on it. |
Save changes | Persists the connection to live setup. Shows Connection settings saved successfully on completion. | Save only after Test connection succeeds for the current values. | Activation of the configuration. Without saving, edits stay local and the connection continues to use the previous values. |
Additional-field editor (administrator)
These fields define what estimators see in the Export to External MIS dialog when they run an export.
Field | What it controls | When to change this | What depends on it |
Display name | The label estimators see on the export dialog (e.g., | When the MIS renames a job-ticket field, or when the existing label is unclear to estimators. | What the estimator sees in the dialog. Which key the additional value lands under in the payload (the integration team maps this in the MIS receiver). |
Type | Validation type the dialog applies to the entered value: Short text, Long text, Number, or Date. | When the MIS expects a different value shape (e.g., a Number where it was a Short text). | Which keyboard / picker the dialog shows. Whether non-numeric values are rejected for Number, and whether Date opens a date picker. |
Is this a required field? | Marks the field Required field or Optional field in the dialog. | When the MIS starts rejecting payloads missing this value, set to Required. When the field becomes nice-to-have, set to Optional. | Whether Confirm export is blocked until the field has a value. Optional field values can be left blank. |
Hide / Show | Toggles visibility without losing the definition. | When you want to stop prompting estimators temporarily, or until the MIS is ready to consume a new field. | Whether the field appears in the dialog the next time an estimator selects Export. Hidden fields are not sent in the payload. |
Remove | Deletes the field after a confirmation prompt. | When the field is permanently no longer needed. | The dialog stops prompting; historical exports keep the captured value, but no future estimate can fill it. |
Estimator-facing surfaces
Surface | What it controls | When to change this | What depends on it |
Export button on the estimate header | Opens the Export to External MIS dialog for a calculated estimate. Hidden when Connection enabled is off, when no Manual trigger is configured, or when the user lacks export permission. | This visibility is set by the Connection enabled switch and Triggers list under Connections — change those, not the button directly. | Whether an estimator can hand off the estimate by hand. |
Export to External MIS dialog | Shows the job summary (Title, Product category, Quantity, Finished size, Price), the additional-field inputs, and the Confirm export action. | Driven by the additional fields configured under Connections. Edit those to change what appears here. | Whether estimators capture the metadata the MIS needs at the moment of export. |
Export Log | Records every export attempt with Success or Failed and the MIS response. Lives in the estimates area. | Read-only for estimators; administrators consult it when an integration looks unhealthy. | The audit trail for support escalation and for verifying automatic-trigger sends. |
Notes on exceptions
The GelatoConnect One destination hides the Triggers, Destination URL, Authentication method, and credential fields — they are owned internally by that integration. Most of this reference applies only to External MIS.
The JSON payload schema (property names, nesting, version) is documented separately by the integration team. This reference covers the configuration UI only; it does not duplicate the schema. Verify the production schema URL with the integration team before sharing it with customers — older internal links pointed at test domains.