Connect your Sekoia DSCR platform to any other application in your stack.
This integration allows you to connect your KMD Sekoia Digital Social Care Records (DSCR) platform to the rest of your software stack using inbound webhooks. Automate the flow of critical care information to streamline operations and ensure data consistency across your organization.
By capturing events in Sekoia—such as newly added care notes, completed tasks, or updated assessments—you can trigger automated workflows in any connected application. This eliminates manual data entry, reduces administrative overhead, and enables real-time data sharing between your care management platform and other core business systems.
Use Flows360 to sync resident profiles, care plans, incident reports, and other key data points with third-party systems for reporting, analytics, or operational coordination. Enhance your data infrastructure and build a more connected, efficient care delivery ecosystem.
Common use cases
- Automated Downstream Reporting: Trigger reports in other systems when care notes, tasks, or assessments are updated in Sekoia.
- Consolidated Resident Records: Sync new resident data from Sekoia to other platforms like CRMs or billing systems.
- Real-time Incident Alerts: When an incident is reported in Sekoia, trigger notifications in communication tools like Slack or Microsoft Teams.
- Unified Care Team Collaboration: Share documents and care plan updates from Sekoia with other systems used by the wider care team.
Sync scenarios
- Sync new residents from Sekoia to a CRM or billing system
- Log care notes created in Sekoia to a data warehouse for analysis
- Trigger alerts in communication platforms when new incidents are reported
- Update records in other systems when assessments are updated or tasks are completed
- Archive documents uploaded to Sekoia in a centralized repository
Objects supported
- Resident
- Care Plan
- Care Note
- Task
- Assessment
- Observation
- Incident
- Employee
- Organization Unit
- Shift
- Medication Administration Record
- Document
Actions
- new_care_note_added
- task_completed
- assessment_updated
- new_incident_reported
- create_care_note
- create_task
- assign_care_plan
- update_resident_profile
- submit_observation
- create_incident_report
- update_task_status
- update_assessment
- new_resident_created
- new_document_uploaded
- observation_reached_threshold
- schedule_shift_task
Frequently asked questions
What data can I sync from Sekoia?
You can sync data related to Residents, Care Plans, Care Notes, Tasks, Assessments, Observations, and Incidents. The integration is triggered by events such as new care notes, completed tasks, or updated assessments.
How does the Sekoia integration work?
The integration uses inbound webhooks to receive real-time event data from your Sekoia instance. When an event occurs in Sekoia, it triggers a workflow in Flows360, which then routes the data to any connected application according to your defined logic.
Is this a two-way integration?
This is a one-way, inbound integration, meaning it primarily receives data from Sekoia. For use cases requiring data to be sent to Sekoia, please contact our solutions team to discuss your requirements.
- Auth method: Inbound Webhook
- Required scopes: 1
- Supported objects: 12
- Supported actions: 16
Overview
This connector allows you to receive real-time event data from your KMD Sekoia Digital Social Care Records (DSCR) platform via inbound webhooks.
By configuring Sekoia to send webhook events, you can capture activities such as new care notes, completed tasks, or updated assessments. This enables you to trigger automated workflows in Flows360, eliminating manual data entry and ensuring data consistency between Sekoia and other connected business systems.
Use these triggers to sync resident profiles, care plans, incident reports, and other key data points with third-party systems for reporting, analytics, or operational coordination.
Setup steps
1. In Flows360, create a new flow and select the Sekoia connector as the trigger.
2. Choose the specific Sekoia event you want to listen for (e.g., 'New Care Note Added').
3. The trigger step will generate a unique Webhook URL. Copy this URL to your clipboard.
4. Log in to your KMD Sekoia administrator account.
5. Navigate to the webhooks or API integration settings section.
6. Create a new webhook subscription.
7. Paste the URL from Flows360 into the 'Endpoint URL' or 'Payload URL' field in Sekoia.
8. Select the corresponding event type in Sekoia that matches your trigger in Flows360.
9. Save and activate the webhook in Sekoia.
10. Perform the action in Sekoia (e.g., add a new care note) to send a test event to Flows360 and confirm the connection.
Required scopes
]
Supported objects
- Resident
- Care Plan
- Care Note
- Task
- Assessment
- Observation
- Incident
- Employee
- Organization Unit
- Shift
- Medication Administration Record
- Document
Supported actions
- new_care_note_added — Triggers when a new care note is created.
- task_completed — Triggers when a task's status is marked as complete.
- assessment_updated — Triggers when an assessment is modified.
- new_incident_reported — Triggers when a new incident report is filed.
- create_care_note — Creates a new care note for a resident.
- create_task — Creates a new task.
- assign_care_plan — Assigns a care plan to a resident.
- update_resident_profile — Updates the profile information for a resident.
- submit_observation — Submits a new observation.
- create_incident_report — Creates a new incident report.
- update_task_status — Changes the status of an existing task.
- update_assessment — Updates an existing assessment.
- new_resident_created — Triggers when a new resident is added to the system.
- new_document_uploaded — Triggers when a new document is uploaded.
- observation_reached_threshold — Triggers when an observation reading crosses a predefined threshold.
- schedule_shift_task — Schedules a new task within a specific shift.
Use cases
- Customer 360
- HR & People Ops
- Data Warehousing
Limitations
This connector is primarily event-driven and relies on inbound webhooks sent from Sekoia to trigger flows. This means that Flows360 can only react to events as they happen in Sekoia and cannot actively poll for new data. The completeness and accuracy of the data received depend on the data payload configured for the webhook in the Sekoia platform. Ensure that the webhook configurations in Sekoia include all necessary data fields for your workflows.