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

How it works

How do Integrations work?

Read the provider's document

Upload the third-party API document. The platform reads it and proposes the registration: endpoint, method, security, request fields and response values.

Register

Review and apply the proposal in the API registry, or fill it in by hand. Keys and passwords stay encrypted on the server.

Choose where it is used

A dropdown filled live; a field that fetches and fills; a button beside a field; a document upload; an automatic workflow step or an incoming callback.

Match fields

A guided editor sets which fields go out and which values come back. AI can propose the matching from a sample.

Test

Try the mapping with a sample response; unknown fields and bad paths are flagged.

Watch

Every call is logged with time, status and result.

Match form fields to what a service sends and returnsA plug board with coloured cables from form fields — pincode, city, state, PAN, name at bank — to the matching values in a service's request and response.Form fieldsService valuesPincodeoutCityinStateinPANoutName at bankin$.pincode$.city$.state$.pan$.nameAtBankAI can propose these matches from a sample response; you review them.
A plug board with coloured cables from form fields to response values.
Five steps to connect any serviceFive tiles: register the service, choose where it is used, match the fields, test with a sample, and watch every call in the log.1RegisterName, address,method2ChooseDropdown, button,upload, step3MatchFields out andback4TestTry a sampleresponse5WatchEvery call logged
Register, Choose, Match, Test, Watch as illustrated tiles.
Every service call is loggedA day's service calls as dots on a timeline — green for success, red for the two that need a look — with one call opened to show the service, case, status and time taken; illustrative.09:0011:0013:0015:0017:00ServiceCredit bureauCaseLO-2026-00042StatusSuccess · 200Took0.4 sToday's service callssuccessneeds a look
A day's calls as green and red dots on a line, one expanded.
A provider's API document becomes a registered serviceA third-party API document listing an endpoint, OAuth 2.0 security, request fields and response values is read by the platform, which proposes a registered service with endpoint, security, fields sent, values returned and timeout, ready to apply and test.Provider's API documentPOST /v2/verifyAuth: OAuth 2.0Request pan, name, dobResponse status, score, refThe platformreads itRegistered serviceproposed for your reviewEndpoint/v2/verify · POSTSecurityOAuth 2.0 client credentialsSends4 fieldsReturns6 valuesTimeout15 s, loggedApplyTest with sampleThe integration becomes configuration — nothing is coded.
A provider's API document read by the platform and turned into a registered service ready to test.

Build your first app free

Up to 10 users. 30 days to build, then 30 days live after go-live.

Start free trialTalk to sales

Updated 30 September 2026