From 3cae4486332e8f2a000f03c93e748f8d9db2cd0c Mon Sep 17 00:00:00 2001 From: daissatou2 <80456839+daissatou2@users.noreply.github.com> Date: Wed, 27 Nov 2024 15:33:07 +0000 Subject: [PATCH 01/13] Update primero.md --- adaptors/primero.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/adaptors/primero.md b/adaptors/primero.md index a1545169db73..155ce35c995b 100644 --- a/adaptors/primero.md +++ b/adaptors/primero.md @@ -63,7 +63,7 @@ See the examples section more sample Primero jobs. ### Integration tips - Data forwarding can be enabled in Primero. There is a webhook that can forward - case information to a designated URL endpoint (e.g., OpenFn Inbox). This data + case information to a designated URL endpoint (e.g., OpenFn Inbox). This feature requires a backend configuration update that the Primero support team can help with. The data forwarding can happen automatically on insert of a new case, as well as on-demand when a user clicks the `Sync` button (which may be added to the page layout if this feature is in use). From 1983b9830331cdbadba152aa8073d9d792602276 Mon Sep 17 00:00:00 2001 From: daissatou2 <80456839+daissatou2@users.noreply.github.com> Date: Wed, 27 Nov 2024 19:36:54 +0000 Subject: [PATCH 02/13] Create asana.md --- adaptors/asana.md | 44 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 adaptors/asana.md diff --git a/adaptors/asana.md b/adaptors/asana.md new file mode 100644 index 000000000000..911d86b020f1 --- /dev/null +++ b/adaptors/asana.md @@ -0,0 +1,44 @@ +--- +title: Asana Adaptor +--- + +## About Asana + +[Asana](https://app.asana.com/) is a web-based project management tool that helps teams organize, plan, collaborate, and execute tasks. + +## Integration Options + +Asana supports 2 primary integration options: + +1. Rest API: Asana has an available REST API that enable external services like OpenFn to pull data from CommCare, or push data from external apps to CommCare. This option is suited for scheduled, bulk syncs or workflows that must update data in CommCare with external information. See [functions](https://docs.openfn.org/adaptors/packages/asana-docs) for more on how to use this adaptor to work with the API. + +2. Webhook: Asana also has a [Webhook or Data Forwarding](https://developers.asana.com/docs/webhooks-guide) to push data from Asana to external systems. This option is suited for real-time, event-based data integration. Check out the Asana [devloper documentation](https://docs.openfn.org/adaptors/packages/asana-docs) to learn how to set up a webhook to push data to OpenFn. + +## Authentication + +See [Asana docs](https://developers.asana.com/docs/authentication) for the latest on supported authentication methods. + +When integrating with Asana via OpenFn, there is one primary authentication method supported: **Personal Access Token (PAT)**. You can generate a personal access token from the Asana [developer console](https://developers.asana.com/docs/personal-access-token). + +See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/asana-configuration-schema) for more on required authentication parameters. + +See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: + +``` +{ + "apiVersion": "1.0", + "token": "sample-tokenyWSJdXBACMLLWMNGgADFA" +} +``` + +### Helpful Links + +1. [API documentation](https://developers.asana.com/docs/overview) + +### Implementation Examples + +1. The Wildlife Conservation Society (WCS) - KoboToolBox -> GoogleSheets -> Asana sync: https://openfn.github.io/ConSoSci/asana/ + + + + From ca4c82e440ebe3975fd0a572d1bb1dc7c5d35944 Mon Sep 17 00:00:00 2001 From: daissatou2 <80456839+daissatou2@users.noreply.github.com> Date: Fri, 29 Nov 2024 18:37:09 +0000 Subject: [PATCH 03/13] Create fhir.md --- adaptors/fhir.md | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 adaptors/fhir.md diff --git a/adaptors/fhir.md b/adaptors/fhir.md new file mode 100644 index 000000000000..5bcaa91afda0 --- /dev/null +++ b/adaptors/fhir.md @@ -0,0 +1,40 @@ +--- +title: FHIR Adaptor +--- + +## About FHIR + +[FHIR](https://www.hl7.org/fhir/overview.html) stands for Fast Healthcare Interoperability Resources. It is a standard for representing and exchanging healthcare data electronically. + +## Integration Options + +**1. Rest API:** The FHIR specification includes a REST API that enables external services like OpenFn to pull data from the FHIR server, or push data from external apps to FHIR servers. This option is suited for scheduled, bulk syncs or workflows that must update data with external information. See [functions](https://docs.openfn.org/adaptors/packages/fhir-docs) for more on how to use this adaptor to work with the API. + +**2. Webhook:** The FHIR specification does not inherently define a webhook or data-forwarding mechanism. However, many FHIR implementations and platforms offer extensions or configurations that support similar functionality. This option is suited for real-time, event-based data integration. Check out the FHIR `Subscription` resource [documentation](https://build.fhir.org/subscription-definitions.html) to learn more about one way this might be implemented. + +## Authentication + +The FHIR standard does not directly prescribe authentication and authorization methods. Instead, it provides security guidelines and leaves the choice of implementation to the developers of FHIR servers and clients. See the FHIR [docs](https://www.hl7.org/fhir/security.html) for the latest security-related recommendations. Depending on the FHIR systems being integrated via OpenFn, you might employ a Basic Auth, API key, or OAuth authentication scheme. + +See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/fhir-configuration-schema) for more on the required authentication parameters. + +See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: + +``` +{ + "baseUrl": "https://hapi.fhir.org", + "apiPath": "baseR4" +} +``` + +### Helpful Links + +1. [API documentation](https://www.hl7.org/fhir/http.html) + +### Implementation Examples + +1. Health in Harmony and ASRI Indonesia- CommCare -> Satusehat sync: [https://openfn.github.io/ConSoSci/arsi/](https://github.com/OpenFn/asri) + + + + From 9d389e288a5c0800c823df8011cc80eb2c2faf24 Mon Sep 17 00:00:00 2001 From: daissatou2 <80456839+daissatou2@users.noreply.github.com> Date: Fri, 29 Nov 2024 18:38:29 +0000 Subject: [PATCH 04/13] Update fhir.md --- adaptors/fhir.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/adaptors/fhir.md b/adaptors/fhir.md index 5bcaa91afda0..54636f9cad93 100644 --- a/adaptors/fhir.md +++ b/adaptors/fhir.md @@ -33,7 +33,7 @@ See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/ ### Implementation Examples -1. Health in Harmony and ASRI Indonesia- CommCare -> Satusehat sync: [https://openfn.github.io/ConSoSci/arsi/](https://github.com/OpenFn/asri) +1. Health in Harmony and ASRI Indonesia- CommCare -> Satusehat sync: [https://github.com/OpenFn/asri](https://github.com/OpenFn/asri) From b200e9426c8fa5c838fb5e3c296e40de6dee8c3c Mon Sep 17 00:00:00 2001 From: daissatou2 <80456839+daissatou2@users.noreply.github.com> Date: Fri, 29 Nov 2024 19:09:31 +0000 Subject: [PATCH 05/13] Create http.md --- adaptors/http.md | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) create mode 100644 adaptors/http.md diff --git a/adaptors/http.md b/adaptors/http.md new file mode 100644 index 000000000000..ab780ae67c19 --- /dev/null +++ b/adaptors/http.md @@ -0,0 +1,38 @@ +--- +title: HTTP Adaptor +--- + +## About HTTP + +[HTTP (HyperText Transfer Protocol)](https://www.cloudflare.com/learning/ddos/glossary/hypertext-transfer-protocol-http/) is a protocol used for transferring data over the web. It defines how messages are formatted and transmitted, and how web servers and browsers should respond to various commands. + +## Integration Options + +**1. Rest API:** HTTP supports standard methods like `GET`, `POST`, `PUT`, and `DELETE` for interacting with web resources. This option is suited for scheduled, bulk syncs or workflows that must update data with external information. See [functions](https://docs.openfn.org/adaptors/packages/http-docs) for more on how to use this adaptor to work with the API. + +**2. Webhook:** HTTP enables real-time communication via webhooks. Check if your source system offers this feature. + +## Authentication + +HTTP itself does not enforce authentication, but many applications that use HTTP implement security mechanisms to control access. Common methods that can be used when integrating with OpenFn include Basic Authentication, API Keys and OAuth. See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/http-configuration-schema) for more on the required authentication parameters. + +See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: + +``` +{ + "username": "test@openfn.org", + "password": "@some(!)Password", + "access_token": "00QCjAl4MlV-WPX", + "baseUrl": "https://instance_name.surveycto.com" +} +``` + + +### Implementation Examples + +1. UNICEF Primero - UNHCR Progres Interoperability: [https://github.com/OpenFn/primero-progres](https://github.com/OpenFn/primero-progres) +2. UNICEF Thailand Primero Interoperability: [https://openfn.github.io/primero-thailand/](https://openfn.github.io/primero-thailand/) + + + + From a969177f921d20151f26ff66181a665121013243 Mon Sep 17 00:00:00 2001 From: daissatou2 <80456839+daissatou2@users.noreply.github.com> Date: Fri, 29 Nov 2024 19:34:22 +0000 Subject: [PATCH 06/13] Create openmrs.md --- adaptors/openmrs.md | 40 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 40 insertions(+) create mode 100644 adaptors/openmrs.md diff --git a/adaptors/openmrs.md b/adaptors/openmrs.md new file mode 100644 index 000000000000..71f1dee385c9 --- /dev/null +++ b/adaptors/openmrs.md @@ -0,0 +1,40 @@ +--- +title: OpenMRS Adaptor +--- + +## About OpenMRS + +[OpenMRS (Open Medical Record System)](https://openmrs.org/) is an open-source platform designed to manage electronic medical records (EMRs) in low-resource environments. It provides a framework that allows developers to extend its core functionality through custom modules and APIs. + +## Integration Options + +**1. Rest API:** OpenMRS offers a REST API that enables external applications to interact with its database and perform bulk operations. This option is ideal for applications requiring scheduled or bulk synchronization with OpenMRS. Refer to the OpenMRS REST API [documentation](https://wiki.openmrs.org/) for detailed guidelines on endpoints and payload formats. + +**2. Webhook:** OpenMRS does not natively support webhooks as a standard feature. However, the platform is highly extensible and allows for customization through its module system. More details can be found on the OpenMRS [documentation page​](https://wiki.openmrs.org/). + +## Authentication + +When integrating with OpenMRS via OpenFn, **Basic Authentication** is supported. See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/openmrs-configuration-schema) for more on the required authentication parameters. + +See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: + +``` +{ + "instanceUrl": "http://openmrs.com/instance/url", + "password":"test", + "username":"test" +} +``` + +### Helpful Links + +1. [OpenMRS Developer Guide](https://openmrs.atlassian.net/wiki/spaces/docs/pages/25476048/Developer+Guide) +2. Community Forums: [OpenMRS Talk](https://talk.openmrs.org/) + +### Implementation Examples + +1. OpenFn Prototype for Médecins Sans Frontières (MSF) LIME Project - OpenMRS -> DHIS2 sync: [https://github.com/OpenFn/openfn-lime](https://github.com/OpenFn/openfn-lime) + + + + From cb499ee978963a2c067d30c7a51c894606300f6a Mon Sep 17 00:00:00 2001 From: daissatou2 <80456839+daissatou2@users.noreply.github.com> Date: Fri, 29 Nov 2024 19:38:39 +0000 Subject: [PATCH 07/13] Update http.md --- adaptors/http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/adaptors/http.md b/adaptors/http.md index ab780ae67c19..3df478ba3dff 100644 --- a/adaptors/http.md +++ b/adaptors/http.md @@ -8,7 +8,7 @@ title: HTTP Adaptor ## Integration Options -**1. Rest API:** HTTP supports standard methods like `GET`, `POST`, `PUT`, and `DELETE` for interacting with web resources. This option is suited for scheduled, bulk syncs or workflows that must update data with external information. See [functions](https://docs.openfn.org/adaptors/packages/http-docs) for more on how to use this adaptor to work with the API. +**1. Rest API:** HTTP supports standard methods like `GET`, `POST`, `PUT`, and `DELETE` for interacting with web resources. This option is suited for scheduled, bulk syncs or workflows that must update data with external information. See [functions](https://docs.openfn.org/adaptors/packages/http-docs) for more on how to use this adaptor to work with the API. Note: This adaptor can be used to communicate w/ any API that supports HTTP. **2. Webhook:** HTTP enables real-time communication via webhooks. Check if your source system offers this feature. From 92f3d022c036ab8180158603a423c50a4849ee94 Mon Sep 17 00:00:00 2001 From: Aleksa Krolls Date: Fri, 29 Nov 2024 23:41:24 +0300 Subject: [PATCH 08/13] Update http.md --- adaptors/http.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/adaptors/http.md b/adaptors/http.md index 3df478ba3dff..2df05861a861 100644 --- a/adaptors/http.md +++ b/adaptors/http.md @@ -2,15 +2,16 @@ title: HTTP Adaptor --- -## About HTTP +## About the HTTP "universal" adaptor -[HTTP (HyperText Transfer Protocol)](https://www.cloudflare.com/learning/ddos/glossary/hypertext-transfer-protocol-http/) is a protocol used for transferring data over the web. It defines how messages are formatted and transmitted, and how web servers and browsers should respond to various commands. +Communicate with web apps using [HTTP (HyperText Transfer Protocol)](https://www.cloudflare.com/learning/ddos/glossary/hypertext-transfer-protocol-http/). +This adaptor enables out-of-box integration with any REST API! ## Integration Options -**1. Rest API:** HTTP supports standard methods like `GET`, `POST`, `PUT`, and `DELETE` for interacting with web resources. This option is suited for scheduled, bulk syncs or workflows that must update data with external information. See [functions](https://docs.openfn.org/adaptors/packages/http-docs) for more on how to use this adaptor to work with the API. Note: This adaptor can be used to communicate w/ any API that supports HTTP. +Use this adaptor to communicate with **any REST API** or any other app that can communicate via HTTP. -**2. Webhook:** HTTP enables real-time communication via webhooks. Check if your source system offers this feature. +**Note that OpenFn also supports Webhooks, but that is a workflow trigger type ([see docs](/documentation/build/triggers#webhook-event-triggers)), not an adaptor.** ## Authentication From 13a741e8eab083546f867df4d8d56e2644379e15 Mon Sep 17 00:00:00 2001 From: Aleksa Krolls Date: Fri, 29 Nov 2024 23:48:37 +0300 Subject: [PATCH 09/13] Update fhir.md --- adaptors/fhir.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/adaptors/fhir.md b/adaptors/fhir.md index 54636f9cad93..0f862d9c24bc 100644 --- a/adaptors/fhir.md +++ b/adaptors/fhir.md @@ -6,6 +6,12 @@ title: FHIR Adaptor [FHIR](https://www.hl7.org/fhir/overview.html) stands for Fast Healthcare Interoperability Resources. It is a standard for representing and exchanging healthcare data electronically. +::: info New adaptor coming soon! + +FHIR version-specific adaptors (e.g., `fhir-r4`) with enhanced functionality are coming soon to fast-track integration setup with more helper functions, templates, and docs than this simple adaptor. See the [Adaptors Wiki](https://github.com/OpenFn/adaptors/wiki/Generating-Fhir-Adaptors) for how to build an adaptor specific to your FHIR Implementation Guide. + +::: + ## Integration Options **1. Rest API:** The FHIR specification includes a REST API that enables external services like OpenFn to pull data from the FHIR server, or push data from external apps to FHIR servers. This option is suited for scheduled, bulk syncs or workflows that must update data with external information. See [functions](https://docs.openfn.org/adaptors/packages/fhir-docs) for more on how to use this adaptor to work with the API. @@ -18,7 +24,7 @@ The FHIR standard does not directly prescribe authentication and authorization m See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/fhir-configuration-schema) for more on the required authentication parameters. -See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: +See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this to define your target endpoint and FHIR version: ``` { @@ -30,11 +36,7 @@ See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/ ### Helpful Links 1. [API documentation](https://www.hl7.org/fhir/http.html) - -### Implementation Examples - -1. Health in Harmony and ASRI Indonesia- CommCare -> Satusehat sync: [https://github.com/OpenFn/asri](https://github.com/OpenFn/asri) - +2. [Digital Square on FHIR](https://digitalsquare.org/resourcesrepository/digital-square-on-fhir-4c78p) From 724ddafd52f046dd2d00454fba30188d7aa0b079 Mon Sep 17 00:00:00 2001 From: Aleksa Krolls Date: Fri, 29 Nov 2024 23:51:50 +0300 Subject: [PATCH 10/13] Update fhir.md --- adaptors/fhir.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/adaptors/fhir.md b/adaptors/fhir.md index 0f862d9c24bc..4d656cee1e93 100644 --- a/adaptors/fhir.md +++ b/adaptors/fhir.md @@ -14,7 +14,7 @@ FHIR version-specific adaptors (e.g., `fhir-r4`) with enhanced functionality are ## Integration Options -**1. Rest API:** The FHIR specification includes a REST API that enables external services like OpenFn to pull data from the FHIR server, or push data from external apps to FHIR servers. This option is suited for scheduled, bulk syncs or workflows that must update data with external information. See [functions](https://docs.openfn.org/adaptors/packages/fhir-docs) for more on how to use this adaptor to work with the API. +**1. Rest API:** The FHIR specification includes a REST API that enables external services like OpenFn to pull data from the FHIR server, or push data from external apps to FHIR servers. This option is suited for scheduled, bulk syncs or workflows that must update data with external information. See [functions](/adaptors/packages/fhir-docs) for more on how to use this adaptor to work with the API. **2. Webhook:** The FHIR specification does not inherently define a webhook or data-forwarding mechanism. However, many FHIR implementations and platforms offer extensions or configurations that support similar functionality. This option is suited for real-time, event-based data integration. Check out the FHIR `Subscription` resource [documentation](https://build.fhir.org/subscription-definitions.html) to learn more about one way this might be implemented. @@ -22,9 +22,9 @@ FHIR version-specific adaptors (e.g., `fhir-r4`) with enhanced functionality are The FHIR standard does not directly prescribe authentication and authorization methods. Instead, it provides security guidelines and leaves the choice of implementation to the developers of FHIR servers and clients. See the FHIR [docs](https://www.hl7.org/fhir/security.html) for the latest security-related recommendations. Depending on the FHIR systems being integrated via OpenFn, you might employ a Basic Auth, API key, or OAuth authentication scheme. -See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/fhir-configuration-schema) for more on the required authentication parameters. +See this adaptor's [Configuration docs](/adaptors/packages/fhir-configuration-schema) for more on the required authentication parameters. -See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this to define your target endpoint and FHIR version: +See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this to define your target endpoint and FHIR version: ``` { From 97038c05872381ccda4bf01dd521018d311185dd Mon Sep 17 00:00:00 2001 From: Aleksa Krolls Date: Fri, 29 Nov 2024 23:52:37 +0300 Subject: [PATCH 11/13] Update asana.md --- adaptors/asana.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/adaptors/asana.md b/adaptors/asana.md index 911d86b020f1..85700e494649 100644 --- a/adaptors/asana.md +++ b/adaptors/asana.md @@ -10,9 +10,9 @@ title: Asana Adaptor Asana supports 2 primary integration options: -1. Rest API: Asana has an available REST API that enable external services like OpenFn to pull data from CommCare, or push data from external apps to CommCare. This option is suited for scheduled, bulk syncs or workflows that must update data in CommCare with external information. See [functions](https://docs.openfn.org/adaptors/packages/asana-docs) for more on how to use this adaptor to work with the API. +1. Rest API: Asana has an available REST API that enable external services like OpenFn to pull data from CommCare, or push data from external apps to CommCare. This option is suited for scheduled, bulk syncs or workflows that must update data in CommCare with external information. See [functions](/adaptors/packages/asana-docs) for more on how to use this adaptor to work with the API. -2. Webhook: Asana also has a [Webhook or Data Forwarding](https://developers.asana.com/docs/webhooks-guide) to push data from Asana to external systems. This option is suited for real-time, event-based data integration. Check out the Asana [devloper documentation](https://docs.openfn.org/adaptors/packages/asana-docs) to learn how to set up a webhook to push data to OpenFn. +2. Webhook: Asana also has a [Webhook or Data Forwarding](https://developers.asana.com/docs/webhooks-guide) to push data from Asana to external systems. This option is suited for real-time, event-based data integration. Check out the Asana [devloper documentation](/adaptors/packages/asana-docs) to learn how to set up a webhook to push data to OpenFn. ## Authentication @@ -20,9 +20,9 @@ See [Asana docs](https://developers.asana.com/docs/authentication) for the lates When integrating with Asana via OpenFn, there is one primary authentication method supported: **Personal Access Token (PAT)**. You can generate a personal access token from the Asana [developer console](https://developers.asana.com/docs/personal-access-token). -See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/asana-configuration-schema) for more on required authentication parameters. +See this adaptor's [Configuration docs](/adaptors/packages/asana-configuration-schema) for more on required authentication parameters. -See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: +See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: ``` { From 7606b3080abba45d3c7bcbfda94de494c3cd2b69 Mon Sep 17 00:00:00 2001 From: Aleksa Krolls Date: Fri, 29 Nov 2024 23:53:27 +0300 Subject: [PATCH 12/13] Update http.md --- adaptors/http.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/adaptors/http.md b/adaptors/http.md index 2df05861a861..295cb231281d 100644 --- a/adaptors/http.md +++ b/adaptors/http.md @@ -15,9 +15,9 @@ Use this adaptor to communicate with **any REST API** or any other app that can ## Authentication -HTTP itself does not enforce authentication, but many applications that use HTTP implement security mechanisms to control access. Common methods that can be used when integrating with OpenFn include Basic Authentication, API Keys and OAuth. See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/http-configuration-schema) for more on the required authentication parameters. +HTTP itself does not enforce authentication, but many applications that use HTTP implement security mechanisms to control access. Common methods that can be used when integrating with OpenFn include Basic Authentication, API Keys and OAuth. See this adaptor's [Configuration docs](/adaptors/packages/http-configuration-schema) for more on the required authentication parameters. -See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: +See platform docs on [managing credentials](/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: ``` { From a92ad823eb1a5a39cc8de7eb588da1815084489d Mon Sep 17 00:00:00 2001 From: Aleksa Krolls Date: Fri, 29 Nov 2024 23:53:58 +0300 Subject: [PATCH 13/13] Update openmrs.md --- adaptors/openmrs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/adaptors/openmrs.md b/adaptors/openmrs.md index 71f1dee385c9..98eb0f3339a6 100644 --- a/adaptors/openmrs.md +++ b/adaptors/openmrs.md @@ -14,9 +14,9 @@ title: OpenMRS Adaptor ## Authentication -When integrating with OpenMRS via OpenFn, **Basic Authentication** is supported. See this adaptor's [Configuration docs](https://docs.openfn.org/adaptors/packages/openmrs-configuration-schema) for more on the required authentication parameters. +When integrating with OpenMRS via OpenFn, **Basic Authentication** is supported. See this adaptor's [Configuration docs](/adaptors/packages/openmrs-configuration-schema) for more on the required authentication parameters. -See platform docs on [managing credentials](https://github.com/OpenFn/docs/blob/main/documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: +See platform docs on [managing credentials](documentation/manage-projects/manage-credentials) for how to configure a credential in OpenFn. If working locally or if using a Raw JSON credential type, then your configuration will look something like this: ``` {