Use HubSpot to prepare a new contact without invented fields
Example: A business receives a customer introduction with a name and email. A template has a phone-number field with no supplied value.
Keep HubSpot as the source for its records. A Righthand can use available information for the decision below.
This article is from Righthand. The example and result are illustrative. This guide has no executed integration test.
The customer task
A business receives a customer introduction with a name and email. A template has a phone-number field with no supplied value.
Provider documentation. The documentation gives information about contact records with properties and associations. For contact operations, applicable scopes and property values are necessary.
Make account access explicit
If HubSpot is available in Connections, connect the intended account. Give the Righthand access to that connection.
Provider documentation does not establish installed Righthand operations. Examine the connection’s available tools before assigning direct account work.
For direct account work, the connection must have the necessary read or write operation and permission. If that operation is unavailable, supply the information in a message. The owner must make any account change in that case.
Connection Permissions gives information about account access and tool permissions. Give only the access necessary for the identified task.
The request to the Righthand
Read the supplied introduction.
>
Prepare the contact with supplied name and email.
>
Leave the phone number unknown.
>
Get approval before creating the record.
>
Send the owner the result before 3 PM Friday.
>
Use Pacific time.
Use the provider records for the result
Identify the contact through an exact reference or verified email. Keep individual properties distinct from company and deal context. Review a proposed change before writing it.
A template field does not establish a value that the customer did not supply.
For a permitted write, examine the resulting account record. A proposal does not establish a completed change.
For an external message, identify the recipient and permitted task. Ask uses an explicit instruction or approval. Connection tool permissions are another required control. Communications Policy.
An illustrative result and next step
The proposed record has the supplied name and email. It contains no invented phone number.
The CRM owner gives approval for creation and gives a decision about whether a phone request is necessary.
Try one account task
- Give the Righthand one identified source record.
- Compare its result with that source.
- Examine the account record after a permitted write.
- Examine the work in Activity.
If a direct operation is unavailable, give the source information in a message. This does not establish a direct integration.
When the account tools are sufficient
Use HubSpot directly when its existing view gives the complete answer and no other conversation is necessary. A person can make the decision from that view.