Skip to main content

2 posts tagged with "Integration"

View All Tags

Pull external data into your register with OpenConnector

· 10 min read
Conduction
Conduction
Open-source workspace stack
Choose how you work

Each step below has three tabs — UI, API, and PHP — so you can follow the click-path, automate it with curl, or call the apps' OCA\ services in code. Pick one and it sticks across every step.

Recommended first

This is Part 4 of the Woo tutorial series. Parts 1, 2 and 3 set up the registers, the files, and the public catalog this tutorial fills.

So far you entered datasets by hand. In production they come from another system: a case-management API, an open-data source, an existing register. In this tutorial you connect one with OpenConnector, through the interface. You build a source, a mapping, and a synchronisation, then run it. External records become datasets in your register.

Build a Nextcloud app on the Conduction stack — Part 6: Integrate

· 16 min read
Conduction
Conduction
Open-source workspace stack

This is Part 6 of the nine-part app-building tutorial series. Part 4 packaged the app and put it on the Conduction store; this part makes it talk to the rest of the workspace: three integration patterns layered from least to most invasive. By the end your orders know who their supplier is, every order shows the right care guide from xWiki, and a needs_followup order automatically opens a maintenance page in xWiki that flips the order back to delivered when the page is marked resolved.

Parts 5 and 6 are parallel

Both build directly on the shipped app from Part 4. Part 5: Advanced manifest features deepens the manifest surface (actionToggles, fieldWidgets, public-mode pages). Part 6 widens to other systems. Take them in either order, or pick whichever your next app actually needs first. Neither references the other for content.

The point isn't the specific integrations, it's the pattern. Cross-register reads are how Conduction apps share data without coupling. The OpenConnector source-and-synchronisation pattern is how you absorb data from anywhere into your own register. The webhook endpoint pattern is how external systems push state back. Once you've wired all three, you've covered the integration vocabulary the rest of the catalogue uses.