Messaging, documents, and calendar work

Create staff follow-up tasks

Create one owner-specific follow-up task associated to a source record.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

Owner and source are required; repeated deliveries return existing or uncertain reconciliation.

What to customize

Set task template, association type ID, and deterministic defaultDueAt.

Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.

Expected outcome

This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.

Sample input

sample-input.json

{
  "inputFields": {
    "field1": "{\"ownerId\":\"u1\",\"sourceId\":\"e1\"}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "planned",
    "output2": "unassigned",
    "output3": "{\"properties\":{\"hs_task_subject\":\"Follow up\",\"hs_task_body\":\"Complete the follow-up\",\"hs_timestamp\":\"2030-01-02T09:00:00.000Z\",\"hubspot_owner_id\":\"u1\",\"hs_task_status\":\"NOT_STARTED\"},\"associations\":[{\"to\":{\"id\":\"e1\"},\"types\":[{\"associationCategory\":\"HUBSPOT_DEFINED\",\"associationTypeId\":204}]}]}"
  }
}

Returned fields

output1: created, existing, planned, uncertain, or error
output2: task ID or reason
output3: JSON task payload

What changes when it runs

Creates a HubSpot task and association in live mode; stores uniqueness key.

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe