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.
Capability summary
Authentication
Auth method: Inbound Webhook
Required scopes
]
Supported objects
| Object | Read | Write | Notes |
|---|---|---|---|
| Resident | Yes | Yes | |
| Care Plan | Yes | Yes | |
| Care Note | Yes | Yes | |
| Task | Yes | Yes | |
| Assessment | Yes | Yes | |
| Observation | Yes | Yes | |
| Incident | Yes | Yes | |
| Employee | Yes | No | |
| Organization Unit | Yes | No | |
| Shift | Yes | Yes | |
| Medication Administration Record | Yes | No | |
| Document | Yes | No |
Supported actions
| Action | Description |
|---|---|
| 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. |
Setup steps
- In Flows360, create a new flow and select the Sekoia connector as the trigger.
- Choose the specific Sekoia event you want to listen for (e.g., 'New Care Note Added').
- The trigger step will generate a unique Webhook URL. Copy this URL to your clipboard.
- Log in to your KMD Sekoia administrator account.
- Navigate to the webhooks or API integration settings section.
- Create a new webhook subscription.
- Paste the URL from Flows360 into the 'Endpoint URL' or 'Payload URL' field in Sekoia.
- Select the corresponding event type in Sekoia that matches your trigger in Flows360.
- Save and activate the webhook in Sekoia.
- Perform the action in Sekoia (e.g., add a new care note) to send a test event to Flows360 and confirm the connection.
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.
Troubleshooting
My flow is not triggering when an event happens in Sekoia. What should I check?
- Verify that the Webhook URL generated by the Flows360 trigger step is identical to the one configured in your Sekoia webhook settings.n2. In Sekoia, check the webhook delivery logs. Look for any HTTP error codes (e.g., 4xx, 5xx) that would indicate a delivery failure.n3. Ensure the webhook in Sekoia is enabled and subscribed to the correct event type that you expect to trigger the flow.n4. Send a test event from Sekoia's webhook configuration page (if available) to confirm the basic connectivity.