CRM Integrations

1. In your Zap, choose the trigger in your CRM that marks a family as ready for aftercare, such as a new contact, a tag, or a stage change.
2. For the action, search for Lasting Aftercare and choose Create Recipient. When Zapier asks for a connection, paste your API key.
3. Map the trigger fields onto the recipient fields, send a test, and turn the Zap on.
4. If you would rather not install our app, add Webhooks by Zapier as the action instead, choose POST, set the payload type to JSON, and add a header named Authorization with the value Bearer followed by your key.

Body for Webhooks by Zapier

{
  "recipientName": "Margaret Ellison",
  "addressLine1": "418 Oak Street",
  "city": "Cedar Rapids",
  "state": "IA",
  "postalCode": "52402",
  "relationship": "wife",
  "subjectName": "David Ellison",
  "dateOfPassing": "2026-03-14",
  "externalId": "12345",
  "externalSource": "zapier"
}

1. Open the workflow that runs when a contact is ready for aftercare, then add the action Send a webhook. That action comes with Data Hub Professional and Enterprise.
2. Set the method to POST and the webhook URL to https://api.lastingaftercare.com/v1/integrations/intake.
3. For authentication, choose API key, set the header name to Authorization, and set the value to Bearer followed by your key.
4. Choose a custom request body and map your contact properties onto the field names in the reference below, using the HubSpot record id as externalId so a re-fired workflow never enrolls the same family twice.

Custom request body

{
  "recipientFirstName": "{{ contact.firstname }}",
  "recipientLastName": "{{ contact.lastname }}",
  "recipientEmail": "{{ contact.email }}",
  "addressLine1": "{{ contact.address }}",
  "city": "{{ contact.city }}",
  "state": "{{ contact.state }}",
  "postalCode": "{{ contact.zip }}",
  "relationship": "{{ contact.relationship_to_deceased }}",
  "subjectName": "{{ contact.deceased_name }}",
  "dateOfPassing": "{{ contact.date_of_passing }}",
  "externalId": "{{ contact.hs_object_id }}",
  "externalSource": "hubspot"
}

1. In Setup, create an External Credential with a custom header named Authorization whose value is Bearer followed by your key, then create a Named Credential that points at https://api.lastingaftercare.com and uses that External Credential.
2. Give the running user permission to the External Credential principal, otherwise the callout is refused at run time.
3. In Flow Builder, add an Action of type HTTP Callout, select the Named Credential, set the method to POST and the path to /v1/integrations/intake.
4. Paste the sample body below when Flow asks for a sample request, so External Services generates the input fields, then map your record values onto them and use the record id as externalId.
5. HTTP Callout in Flow is available on Enterprise, Unlimited and Performance editions.

Sample request body for the callout

{
  "recipientName": "Margaret Ellison",
  "addressLine1": "418 Oak Street",
  "addressLine2": "Apt 2",
  "city": "Cedar Rapids",
  "state": "Iowa",
  "postalCode": "52402-1183",
  "recipientEmail": "[email protected]",
  "relationship": "wife",
  "subjectName": "David Ellison",
  "dateOfPassing": "2026-03-14",
  "externalId": "0035g00000AbCdEfGHI",
  "externalSource": "salesforce"
}

1. Go to Setup, then Automation, then Workflow Rules, and open or create the rule that should enroll a family.
2. Add an instant action of type Webhook, set the method to POST and the URL to https://api.lastingaftercare.com/v1/integrations/intake.
3. Under header parameters, add Authorization with the value Bearer followed by your key.
4. Choose a raw JSON body and build it with merge fields from the Contacts module. Zoho allows ten merge fields per webhook, which covers the required set with room left for externalId.

Raw JSON body with merge fields

{
  "recipientName": "${Contacts.Full Name}",
  "addressLine1": "${Contacts.Mailing Street}",
  "city": "${Contacts.Mailing City}",
  "state": "${Contacts.Mailing State}",
  "postalCode": "${Contacts.Mailing Zip}",
  "relationship": "${Contacts.Relationship}",
  "subjectName": "${Contacts.Deceased Name}",
  "dateOfPassing": "${Contacts.Date of Passing}",
  "externalId": "${Contacts.Contact Id}",
  "externalSource": "zoho"
}

1. In the workflow that should enroll a family, add the action Custom Webhook. Your agency turns premium actions on for the sub-account before that action appears in the list.
2. Set the method to POST and the URL to https://api.lastingaftercare.com/v1/integrations/intake.
3. For authentication, choose Bearer token and paste your key on its own, with no prefix, since HighLevel adds the word Bearer for you.
4. Set the body type to JSON and fill each value with a merge tag from the contact record, using the contact id as externalId.

JSON body with merge tags

{
  "recipientFirstName": "{{contact.first_name}}",
  "recipientLastName": "{{contact.last_name}}",
  "recipientPhone": "{{contact.phone}}",
  "addressLine1": "{{contact.address1}}",
  "city": "{{contact.city}}",
  "state": "{{contact.state}}",
  "postalCode": "{{contact.postal_code}}",
  "relationship": "{{contact.relationship}}",
  "subjectName": "{{contact.deceased_name}}",
  "dateOfPassing": "{{contact.date_of_passing}}",
  "externalId": "{{contact.id}}",
  "externalSource": "highlevel"
}

1. Follow Up Boss has no outbound webhook action inside the product, so the connection runs through Zapier.
2. Create a Zap with Follow Up Boss as the trigger and pick one of the instant triggers, such as Tag Added to Contact or Person Stage Updated, so the Zap fires the moment your team marks the record.
3. For the action, choose Lasting Aftercare and Create Recipient, then connect it with your API key.
4. Map the name and mailing address from the person record, add the details of the person the cards honor, and map the Follow Up Boss person id onto externalId.

Fields the Create Recipient action sends

{
  "recipientName": "Margaret Ellison",
  "addressLine1": "418 Oak Street",
  "city": "Cedar Rapids",
  "state": "IA",
  "postalCode": "52402",
  "relationship": "wife",
  "subjectName": "David Ellison",
  "dateOfPassing": "3/14/2026",
  "externalId": "98765",
  "externalSource": "followupboss"
}