JobNimbus Integration - Jobs

What information is required to have a job created in OCC?

In order for a job to be created in OCC, the following data elements must be completed:

1. The user from JobNimbus MUST be mapped to a user in OCC and their mapping must be active.
2. We make an api call to the contacts OR jobs endpoint those that were updated since the last sync.
3. Depending on the configuration (Job or Contact) the following mappings will be utilized:
   1. Integration configured as Job Type:
      1. Customer Name: {job.name}
      2. Name: {job.contact.first_name} {job.contact.last_name}
      3. Email: {job.email}
      4. Lead Source: {job.source_name}
      5. Job Address:
         1. Line 1: {job.address_line1}
         2. Line 2: {job.address_line2}
         3. City: {job.city}
         4. State: {job.state_text} (which is mapped to the appropriate value based on a lookup)
         5. Postal Code: {job.zip}
      6. Phone Number (we iterate over home_phone, mobile_phone, work_phone, and fax_number):
         1. Name: {phone_type} (Remove the underscore and capitalize e.g. home_phone would be Home phone)
         2. Number: {contact.phone_type} (e.g. the number)
      7. Assigned User: {job.sales_rep}
      8. Metadata:
         1. job_nimbus_job_id: {job.jnid}
         2. job_nimbus_contact_id: {job.primary.id}
         3. job_nimbus_user_id: {job.sales_rep.id}
      9. Appointment:
         1. Start Time: {task.date_start}
         2. End Time: {task.date_end} (unless the end date’s difference is greater than > 7200 or < 0 … in that case it adds 7200 to the date_start)
         3. Appointment Note Text: {task.description)
         4. Metadata:
            1. job_nimbus_event_id: {task.jnid}
   2. Integration configured as Contact Type:
      1. Customer Name: {contact.first_name} {contact.last_name}
      2. Name: {contact.first_name} {contact.last_name}
      3. Email: {contact.email}
      4. Lead Source: {contact.source_name}
      5. Job Address:
         1. Line 1: {contact.address_line1}
         2. Line 2: {contact.address_line2}
         3. City: {contact.city}
         4. State: {contact.state_text} (which is mapped to the appropriate value based on a lookup)
         5. Postal Code: {contact.zip}
      6. Phone Number (we iterate over home_phone, mobile_phone, work_phone, and fax_number):
         1. Name: {phone_type} (Remove the underscore and capitalize e.g. home_phone would be Home phone)
         2. Number: {contact.phone_type} (e.g. the number)
      7. Assigned User: {job.sales_rep}
      8. Metadata:
         1. job_nimbus_job_id: nill
         2. job_nimbus_contact_id: {contact.id}
         3. job_nimbus_user_id: {contact.sales_rep.id}
      9. Appointment:
         1. Start Time: {task.date_start}
         2. End Time: {task.date_end} (unless the end date’s difference is greater than > 7200 or < 0 … in that case it adds 7200 to the date_start)
         3. Appointment Note Text: {task.description)
         4. Metadata:
            1. job_nimbus_event_id: {task.jnid}

Are there any options for other mappings for job creation?

No, there aren’t any other options for data mappings or job creation other than Job vs Contact.

When should an update in JobNimbus be reflected in OCC?

There is a job that runs every 15 minutes at 5, 20, 35, and 50 minutes after the hour.

What happens if an Opportunity or Contact is deleted in JobNimbus?

The information created in OCC would be orphaned and unlinked between JobNimbus and OCC. There is no update to reflect that in OCC and no updates will be pulled to a job(s) in OCC.

What happens if an Appointment is deleted in JobNimbus?

Much like if a Contact or Job is deleted in JobNimbus, NO update for appointment(s) will be pulled to a job(s) in OCC.

Do updates in OCC push back to JobNimbus?

No, there are no updates which are made in OCC pushed back to JobNimbus.

Can I make status changes in OCC and have them show up in JobNimbus?

No, not at this time.

What happens when I change the assigned user on the Contact or Job in JobNimbus?

Once a Job or Contact has the assigned sales rep changed to a different user it should be picked up on the 15 minute synchronization timeframe. Please note the SAME rules still exist where there must be a user linked between OCC and JobNimbus.