WEBVTT

1
00:00:00.200 --> 00:00:07.079
A CRM connection lets a form or workflow send
information to the system your team already uses.

2
00:00:07.259 --> 00:00:09.683
This lesson explains the setup sequence.

3
00:00:09.863 --> 00:00:15.056
Start with a dedicated test account, and use fictional records while you check the process.

4
00:00:15.516 --> 00:00:25.104
Before connecting, confirm that the connector is available for your Klarstig.ai
account and that your CRM subscription permits the required access.

5
00:00:25.284 --> 00:00:31.160
Authentication, record updates, prefill, and
document attachments are separate capabilities.

6
00:00:31.340 --> 00:00:35.309
A connection alone does not establish that all four are supported.

7
00:00:35.769 --> 00:00:41.015
In Klarstig.ai, open Integrations and the CRM connection page.

8
00:00:41.195 --> 00:00:45.963
Choose the provider and give the connection a clear name, such as CRM Training.

9
00:00:46.143 --> 00:00:53.833
Keep test and customer environments clearly identified
so you can recognize the destination before sending data.

10
00:00:54.293 --> 00:00:59.529
For an OAuth connection, continue through the provider's secure authorization page.

11
00:00:59.709 --> 00:01:03.506
Select the intended account and review the requested permissions.

12
00:01:03.686 --> 00:01:07.303
Some providers use a secure credential form instead.

13
00:01:07.483 --> 00:01:13.979
Enter credentials only in the designated secure
form, never in a form response or support message.

14
00:01:14.439 --> 00:01:17.725
If authorization fails, read the specific message.

15
00:01:17.905 --> 00:01:22.109
A redirect mismatch belongs to the OAuth app configuration.

16
00:01:22.289 --> 00:01:25.947
Access denied points to permissions or the selected account.

17
00:01:26.127 --> 00:01:30.234
Expired or revoked access may require a secure reconnect.

18
00:01:30.414 --> 00:01:33.261
Repeated clicking will not correct those settings.

19
00:01:33.721 --> 00:01:38.477
After authorization returns you to Klarstig.ai, run Test connection.

20
00:01:38.657 --> 00:01:42.103
Read the result and confirm which account is connected.

21
00:01:42.283 --> 00:01:50.548
A successful authentication check is useful evidence, but it does
not prove that a form mapping or a record delivery has succeeded.

22
00:01:51.008 --> 00:01:58.612
Before using customer data, load the actual CRM fields
and test one supported record action with fictional data.

23
00:01:58.792 --> 00:02:02.195
Verify the resulting record inside the CRM.

24
00:02:02.375 --> 00:02:08.891
Use the record identifier and delivery details to
connect that result to the submission that produced it.

25
00:02:09.351 --> 00:02:15.345
Your next step is to choose one form, one CRM object, and the fields you intend to send.

26
00:02:15.525 --> 00:02:19.001
Continue with Map Form Fields to CRM Fields.

27
00:02:19.181 --> 00:02:24.942
The written lesson and this narration are available together in Klarstig.ai Academy.