Map lead fields, sources and staff correctly

Where to start
CRM workspace → Tools → Britixo Automations (or Utilities in a classic layout)

Before you begin

Use the field names exposed by the approved app. Ask your integrator before sending raw API fields, custom-field values or record IDs from another workspace.

Follow these steps

1. Map name first, then email and phone where needed. Use plain text for ordinary contact and company fields.
2. Choose source, status and assigned staff from the connected workspace’s current options.
3. Map address fields separately: address, city, state, zip and country. Country is a numeric CRM country identifier in the API, not a free-text country name.
4. Keep descriptive text and tags purposeful. Review the destination’s field type and length as well as the CRM field.
5. Create a labelled test lead and compare every mapped value with the saved CRM record, including any truncated text or fallback selection.

If something does not look right

If data is truncated, a country is wrong or a numeric ID resolves unexpectedly, stop and correct the mapping. Do not reuse IDs copied from another company or assume a field is supported because it exists elsewhere in the CRM.

Fields, rules and limits

• Supported create fields are name, title, company, description, country, zip, city, state, address, assigned, status, source, email, website, phonenumber and tags.
• Current text limits include title/company 191, zip 32, city/state 100, website 150 and phone 50 bytes. Several values are truncated to fit rather than rejected.
• Custom fields, monetary lead value, currency, attachments and customer conversion are not exposed by this create action.
• Treat IDs and flags as their documented types. Do not send arrays or objects into a plain-text field.

Questions and answers

Is phonenumber the same as phone?

The raw API field is phonenumber. The approved app may display a friendlier label; use its mapping rather than inventing an extra phone field.

Can I send a country name such as United Kingdom?

The raw country field expects the CRM’s numeric country ID. Have the approved app or integrator map a recognised country choice correctly.

Can I send custom fields?

Not through the currently documented Create Lead field allowlist. Request an explicitly supported extension if custom-field mapping is needed.

Are tags supported?

The raw action accepts tags as a comma-separated value or an array that is combined into a tag string. Follow the field format provided by your approved app and inspect the saved tags.

Can I map a lead value or currency?

Those fields are not included in this connector’s current Create Lead allowlist. Do not assume that an unknown field is stored.

Can I upload documents or attachments?

The current lead action does not provide an attachment upload endpoint.

Why is long text shorter in the saved record?

Some fields are trimmed to their configured byte length. Shorten the source value deliberately and verify the result, especially for multibyte characters.

Does the connector make new leads public?

It sets the new lead’s public flag to off. Do not rely on an incoming is_public value to override this behaviour.

Useful next steps

• Find a lead before taking action
• Test and publish a Zap safely
• Understand queued events, retries and delays

Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.