DO ONE THING WELL
Connect Your CRM: Setup Essentials
Listen to this guide
English narration. Duration shown in the player.
Read the narration transcript
A CRM connection lets a form or workflow send information to the system your team already uses. This lesson explains the setup sequence. Start with a dedicated test account, and use fictional records while you check the process.
Before connecting, confirm that the connector is available for your Klarstig account and that your CRM subscription permits the required access. Authentication, record updates, prefill, and document attachments are separate capabilities. A connection alone does not establish that all four are supported.
In Klarstig, open Integrations and the CRM connection page. Choose the provider and give the connection a clear name, such as CRM Training. Keep test and customer environments clearly identified so you can recognize the destination before sending data.
For an OAuth connection, continue through the provider's secure authorization page. Select the intended account and review the requested permissions. Some providers use a secure credential form instead. Enter credentials only in the designated secure form, never in a form response or support message.
If authorization fails, read the specific message. A redirect mismatch belongs to the OAuth app configuration. Access denied points to permissions or the selected account. Expired or revoked access may require a secure reconnect. Repeated clicking will not correct those settings.
After authorization returns you to Klarstig, run Test connection. Read the result and confirm which account is connected. A successful authentication check is useful evidence, but it does not prove that a form mapping or a record delivery has succeeded.
Before using customer data, load the actual CRM fields and test one supported record action with fictional data. Verify the resulting record inside the CRM. Use the record identifier and delivery details to connect that result to the submission that produced it.
Your next step is to choose one form, one CRM object, and the fields you intend to send. Continue with Map Form Fields to CRM Fields. The written lesson and this narration are available together in Klarstig Academy.
Watch the narrated slides
Music: A Kind Of Hope by Scott Buckley, licensed under CC BY 4.0. Edited for length, fades and background level.
Prepare the right account, authorize access, and understand what a connection test proves.
Start with the right connection
A CRM connection lets a form or workflow send information to the system your team already uses. This lesson explains the setup sequence. Start with a dedicated test account, and use fictional records while you check the process.
- Use a CRM test account
- Keep customer data out of practice
- Confirm the intended destination
Confirm what is available
Before connecting, confirm that the connector is available for your Klarstig account and that your CRM subscription permits the required access. Authentication, record updates, prefill, and document attachments are separate capabilities. A connection alone does not establish that all four are supported.
- Check the connector in your account
- Confirm the CRM plan allows API access
- Check each capability separately
Choose and name the connection
In Klarstig, open Integrations and the CRM connection page. Choose the provider and give the connection a clear name, such as CRM Training. Keep test and customer environments clearly identified so you can recognize the destination before sending data.
- Open Integrations → CRM
- Choose the provider
- Use a clear name, such as CRM Training
Authorize the intended account
For an OAuth connection, continue through the provider's secure authorization page. Select the intended account and review the requested permissions. Some providers use a secure credential form instead. Enter credentials only in the designated secure form, never in a form response or support message.
- Use the secure connection flow
- Select the intended CRM account
- Review the requested access
Resolve setup errors at the source
If authorization fails, read the specific message. A redirect mismatch belongs to the OAuth app configuration. Access denied points to permissions or the selected account. Expired or revoked access may require a secure reconnect. Repeated clicking will not correct those settings.
- Redirect mismatch → app registration
- Access denied → account permissions
- Expired access → secure reconnect
Run the connection test
After authorization returns you to Klarstig, run Test connection. Read the result and confirm which account is connected. A successful authentication check is useful evidence, but it does not prove that a form mapping or a record delivery has succeeded.
- Run Test connection
- Check the returned result
- Confirm the connected account
Prove the next step separately
Before using customer data, load the actual CRM fields and test one supported record action with fictional data. Verify the resulting record inside the CRM. Use the record identifier and delivery details to connect that result to the submission that produced it.
- Load the actual CRM fields
- Test one supported record action
- Verify the result inside the CRM
Your next step
Your next step is to choose one form, one CRM object, and the fields you intend to send. Continue with Map Form Fields to CRM Fields. The written lesson and this narration are available together in Klarstig Academy.
- One form
- One CRM object
- A short list of approved fields
Examples illustrate decisions and do not report a completed CRM transaction.