DynamicForm Start free trial
Step 10 of 15 · Integrations · topic 2 of 8

Control · Integrations

Set up a connection, one step at a time.

You can begin even when the provider has supplied incomplete instructions. The engine shows what it knows, asks for the missing details and helps your team test the connection before using it for real work.

In short

Work through setup, match the fields and test the results. Your team approves the connection before it goes live, then monitors how it runs.

Steps

Give what you have

Upload the instructions, files or examples supplied by the service provider. The engine reads structured files directly and uses AI to extract details from written documents. Uploaded content is treated as information to inspect, so instructions hidden inside a document cannot direct the AI.

Read the gaps

The Gap Report separates confirmed details from assumptions and information that is missing. Each item points to its source, such as a document page or example request. If two sources disagree, your team can see the conflict; exposed passwords are moved to protected storage and removed from the configuration.

Answer guided questions

The AI guides you through 11 stages, covering the purpose, security, data, testing and other setup decisions. You can answer in everyday language or say you do not know. Any default used to keep setup moving is recorded as an assumption, together with its risk and how it will be checked.

Register and map

Review the available operations, meaning the actions the service can perform, and how the connection signs in. Then map the fields: match each value in your form to the field the provider expects. The AI can suggest these links, but they remain dashed on the canvas until your team accepts them.

Mock and test

Try prepared replies called mocks, or use the provider test environment, called a sandbox. Check what happens when the service succeeds, fails or takes too long, using invented data. Save useful runs as test cases so your team can repeat the same checks after a change.

Choose the use

Choose where the connection should run, such as a button, a field change or a workflow step. For each possible result, choose what happens next: fill a field, show a message, wait, or send the case down a different path. The same connection can be used in more than one place.

Approve and publish

Review the settings, test results and outstanding assumptions before asking for approval. High-risk assumptions must be verified before production; other assumptions must be verified or accepted by an approver. The final approver publishes the connection for real use.

Watch and improve

Monitor the requests sent to the service and the results it returns. Alerts help your operations team notice failures, slow replies or other problems. A call trace records what happened during a request, with personal information hidden, so the team can investigate and propose a new version when needed.

Review the evidence

Gap Report lists known, assumed and missing facts, a URL conflict and a removed secret.
The report separates supported facts from assumptions and missing details. Notice the conflicting base addresses and the removed secret: these are issues for the team to review before relying on the settings.
Provider workspace shows operations, pending changes, write-only credentials and versions.
The workspace brings together available service actions, proposed changes and versions. Credentials are entered separately for each environment, helping your team distinguish test access from live access.
Mapping canvas links form fields through transformations to provider fields.
Follow the links from your form fields through any format changes to the provider fields. The dashed suggestions need acceptance, and the required field without a source needs attention before the request can be completed.

Test before use

Mock Studio lists request and response sets with an outcome coverage strip.
Each mock set provides a prepared request and reply for a particular result. Use the coverage strip to find outcomes that still need an example, so you can check more than the successful path.

Example · Customer Loan Origination

The loan example checks which screen fields are filled by a sample reply, using invented data. The test console shows the request with personal information hidden, so the team can inspect how the connection behaved.

Test console shows a successful mock run, trace identifier and masked request.
The console shows what was sent, what came back and how the response was mapped. Personal information is hidden, while the trace identifier gives your team a reference for investigating the run.

See the full loan example

One call, start to finish

One call, start to finishA server-side call checks inputs, selects a provider, maps and limits the request, authenticates, calls, classifies, handles resilience, fills fields and records a masked trace.1. Check inputs2. Choose provider3. Transform fields4. Apply limits5. Sign in6. Call service7. Classify outcome8. Retry or fail over9. Fill fields10. Log masked
One call, start to finish

Check readiness before moving forward

Mock, Sandbox and Production are separate stages of readiness. Before a provider version moves to Sandbox, every operation needs a passing saved mock test. Before it moves to Production, every operation needs a passing saved sandbox test. This gives reviewers evidence from both a simulated reply and the provider test system.

The readiness checklist also shows missing credentials and outstanding assumptions. The approval request keeps the settings, test evidence and differences reviewers saw, and the final publication checks readiness again.

Build your first app free

All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.

Explore DynamicForm

Compliance · Rules and calculations

Updated 16 November 2026