Would you use a ViewChild, and get the nativeElement?
In the component API, note that the key is how you will access it in your code, the value passed to ViewChild is the "#" id you gave the component (this is ES6, in TS you'd use the ViewChild annotation):
...
queries { 'myElement' : new ViewChild ( 'myelement' ) }
...
In the markup:
<div #myelement></div>
In your component function (a handler, wherever you need to grab it), the nativeElement property gives you a reference to the HTML element, so you can set innerHTML, add a handler, or whatever else you need to do. There's of course other ways to do this by binding to properties (e.g. you can bind to (click) or [innerHTML]):
...
this.myElement.nativeElement... // etc.
...
Alternatively, if you wanted to use a single handler for multiple elements (say, a bunch of different clickable divs) you could use event.target to do the same thing. The problem with that is, because giving IDs is considered "bad" these days, you have to have an alternative way of IDing which DIV got clicked. You can check the label (innerHTML), you can give it a dummy style and check for that, etc.