The Create Contact in BigChange action allows your workflow to automatically create a new contact in your BigChange account, saving time and ensuring consistency across systems.
This is especially useful when dealing with new leads or customers who aren’t yet in your CRM.
Instead of manually entering contact details, your workflow can capture key information (like name, email, and phone number) from earlier steps in your workflow, and use it to create the contact automatically.
This action ensures your contact list stays up to date without manual input, and helps prepare your records for further automation, such as job creation or communication flows.
📚 Learn more about creating a contact in BigChange in this article.
Configuration
To set up the Create Contact in BigChange node:
- Add the node to your workflow, ensuring it is connected to a starting action or another action node.
- Click on the node to open the Properties panel.
Mandatory fields
To successfully create a contact in BigChange, the following fields must be configured:
- Name
- Contact Group
- Address
- Postcode
The Name, Address and Postcode fields will commonly be mapped with variables using data captured earlier in your workflow.
BigChange limits a contact’s name to 50 characters, and this can’t be increased. If the name you map is longer, BigChange won’t accept it
📚 Learn more about working with variables here.
⚠️ Note: BigChange requires every contact to be assigned to a Contact Group.
There are two ways to do this:
- Static assignment: If all contacts in this workflow go to the same group, manually enter the Contact Group name in the Contact Group field. (Note: the name is case-sensitive.)
- Dynamic assignment: If the Contact Group depends on earlier workflow data, use a Conditional Value node to route contacts to the appropriate group using conditions.
📚 Learn more about the Conditional Value node here.
Optional fields
You can optionally configure these fields to enrich your contact record:
- Reference
- Phone
- Parent Contact
The Phone field expects a phone number. If you map a variable, set its data type to Phone in the step that creates it, such as an Extract Text or AI Prompt node. If it’s set to Text, the workflow shows an error
Custom fields
If you use Custom fields in your BigChange contact records, you can populate these too.
📚 Learn more about adding custom fields to your BigChange contacts in this article.
To include custom fields whenever a new contact is automatically created in BigChange by Build Concierge:
- Click + Add under the Custom Fields section.
- Copy and paste the field name of your custom field exactly as it appears in your BigChange account.
- Define the value with a static assignment or map it using a variable.
⚠️ Note: Be sure to match the field name exactly as it appears in your BigChange settings, including spaces and casing, to ensure proper mapping.
An example of a custom field you might use when creating contacts in BigChange is where each new contact should be assigned to a particular Sales Manager. You might want to add this custom field so it is already populated whenever a new contact is created.
Additional fields
Additional fields let you send information to BigChange that doesn’t have its own field on the node. You can pass any contact field that the BigChange API supports, even if it isn’t listed above.
Use additional fields when:
- the information you need isn’t one of the node’s standard fields, and
- it isn’t a custom field you created in BigChange. For those, use Custom fields instead.
To include additional fields whenever a new contact is automatically created in BigChange by Build Concierge:
- Click + Add under the Custom Fields section.
- Enter the field name exactly as the BigChange API expects it.
- Set the value, either static text or a variable from an earlier step.
- Save the node.
Note: Field names must match the BigChange API exactly, including spelling and capitalisation. If a name is wrong, BigChange may ignore it or reject the contact. See BigChange’s contact-save documentation for the full list of supported fields.
Outputs
Once the Create Contact in BigChange node runs, it will return one of two possible outcomes:
- Complete – The contact was successfully created in BigChange. The workflow will continue to the next connected step.
- Failed – The contact could not be created, usually due to incorrect configuration.
💡 Tip: To be told when a workflow fails, turn on Enable error emails in the workflow’s Workflow Configuration sidesheet. The email tells you the reason, which action failed, and links to the execution log. See Failed Workflow Notifications.
Default variables
There is only one variable which is available for use further down the workflow coming from the Create contact in BigChange node. That is:
Contact ID - The ID given to the contact that was created in BigChange.
This can then be used further down the workflow, e.g. to map the Contact ID field in the Create Job in BigChange action node.