Fields that Sync with PieSync

When connecting your data to other services through pie sync, these are the fields that will stay synced between your connected Brivity CRM and other services. 

1. anniversary string
example: 2014-07-10

2. birthdate string
example: 1980-02-13

3. company string
example: Acme

4. description string
example: longer bit of text that can store really any text data that you want associated with the lead

5. email_address string($email)
example: user@home.com
note this field is read only, the primary email is set as a function of the crm system - specific emails are defined by their specifically labeled fields

6. email_address_category string
example: personal
note this field is read only, the category of the primary email is set as a function of the crm system - specific emails are defined by their specifically labeled fields

7. email_status string
example: Active
note this field is read only, it is intended to let you know if the lead has unsubscribed from emails. It is nil when the lead has no email associated. Enum:
[ Active, Unsubscribed, nil ]

8. facebook string
example: https://www.facebook.com/benkinneyrealestateteam/

9. first_name string
example: Michael
user first name

10. home_phone string
example: (407) 970-6612

11. home_street_address string
example: 123 Fake St

12. home_city string
example: Atlanta

13. home_locality string
example: GA
the locality field is often the state, but can also be used for province and country

14. home_postal_code string
example: 33345

15. id integer
example: 1234
note this field is read only - integer id of the lead, the uuid is most often used but this is sometimes required by some of our older systems

16. instagram string
example: @benkinneycompanies

17. intent string
example: seller
the intent of the lead - buyer, seller, tenant, seller/buyer
Enum: [ seller, buyer, seller/buyer, tenant, n/a ]

18. job_title string
example: CTO

19. kids string
example: Jack, Jill

20. last_name string
example: Orr
user last name

21. linkedin string
example: https://www.linkedin.com/in/benkinney

22. mailing_street_address string
example: PO Box 12356

23. mailing_city string
example: Atlanta

24. mailing_locality string
example: GA
the locality field is often the state, but can also be used for province and country

25. mailing_postal_code string
example: 33345

26. marital_status string
example: Married
Enum:
[ Married, Single ]

27. mobile_phone string
example: (407) 970-6613

28. other_email string($email)
example: user@other.com

29. other_phone string
example: (407) 970-6615

30. other_street_address string
example: 123 Other St

31. other_city string
example: Atlanta

32. other_locality string
example: GA
the locality field is often the state, but can also be used for province and country

33. other_postal_code string
example: 33345

34. personal_email string($email)
example: user@home.com

35. pets string
example: James Dean, Sammy Davis Jr

36. phone_number string
example: (111) 111-1111
this field is read only - lead phone number - this is the primary phone number

37. primary_agent_id integer
example: 345111929
returns the id of primary agent, though when submitting a lead you may supply a uuid here or the id of the primary agent. This field is of particular importance. The primary agent essentially owns the lead. If you intend for this lead to be owned by the logged in user, then their id should be submitted in this space.

38. primary_agent_uuid string
example: 345116bf-44cd-4fa6-9419-c211929f243e
note this field is read only - uuid of primary agent

39. primary_agent_name string
example: Epicurian Admin
note this field is read only - name of primary agent

40. source_id integer
example: 973347060
note this field is read only - id of source

41. source string
example: Brivity IDX
name of the source

42. status string
example: hot
status of the lead
Enum:
[ new, unqualified, watch, nurture, hot, past, pending, prospective-client, active, inactive, archived, trash ]

43. submitted_at string
example: 2018-07-17T07:39:54.559-07:00
note this field is read only - date and time lead submitted

44. tags array
array of tags applied to the lead
string
example: [tag1]

45. timezone string
example: Eastern Time (US & Canada)
Enum:
[ Alaska, Central Time (US & Canada), Eastern Time (US & Canada), Indiana (East), Hawaii, Mountain Time (US & Canada), Arizona, Pacific Time (US & Canada) ]

46. twitter string
example: @benkinneyteam

47. type_name string
example: lead
name of type
Enum:
[ lead, sphere, collaborator, team ]

48. uuid string
example: 3a5f0b69-6fa6-447a-b037-f5f853a93b64
note this field is read only - lead uuid

49. work_email string($email)
example: user@work.com

50. work_phone string
example: (407) 970-6614

51. work_street_address string
example: 124 Fake St

52. work_city string
example: Atlanta

53. work_locality string
example: GA
the locality field is often the state, but can also be used for province and country

54. work_postal_code string
example: 33345