Automated activity imports in Pear Suite allow organizations to trigger the same powerful automations used in manual visits, such as creating goals, scheduling follow-ups, or updating member records. By enabling Auto-Actions in your import templates, you can maintain consistent care coordination and data management while processing high volumes of member data.

Step 1 – Configure a scripted flow with actions

1. Build the automated actions you want to trigger (e.g., "Create a Goal") within a Scripted Flow template.
2. Attach this scripted flow to a specific Activity Template.
3. Review the supported actions for imports:
   • Supported: Create/Complete a Goal, Schedule an Activity (immediate only), Create Referral, Start/Update Care Pathway, Assign/Unassign User, and Add/Remove Member from Group.
   • Not Supported: File uploads, future-dated activity scheduling, and member-level flags.

Step 2 – Create an activity import template

1. Navigate to Data Management > Import Templates and click Create Import Template.
2. Choose Activity as the Import Type and select the activity template containing your scripted flow.
3. Name your template and toggle Enable Auto Actions to ON.
   • Note: You can turn this off at any time if you wish to import data without triggering automations.
4. Complete the setup by including unique member identifiers, activity times, and any required billing details (e.g., diagnosis codes).
5. Click Create Import Template to save.

Step 3 – Prepare and map your CSV data

1. Download your template headers to ensure your CSV file matches the platform's requirements exactly.
2. Input the member data and ensure the answers to the flow questions in your CSV match the trigger conditions defined in your scripted flow.
3. Save the file as a CSV (Comma-Separated Values).

Step 4 – Execute the import and verify actions

1. Open the import template you created and go to the Imports tab.
2. Click Create New Import and upload your CSV file.
3. Click Refresh to process the data.
4. The system will generate activities for each member, and the linked auto-actions will run immediately if the data matches the flow’s logic.