Call a Child Component Method from a Parent in Angular

You will learn why Angular components should not usually be created with new, how to reference a child rendered in a parent template with @ViewChild, and when that reference becomes available. You will also see how Angular updates the child view after its component state changes.

Angular creates and manages component instances from component selectors in templates. That management includes dependency injection, lifecycle hooks, change detection, and connecting the instance to its rendered DOM.

When code runs new NotifyComponent(), TypeScript creates an ordinary class object. Its callMethod() can run, so console.log() works and this.test changes on that object. However, it is not the same instance as the one Angular rendered, and Angular has not connected it to a <notify> view. Therefore, no visible template changes.

To let a parent access a child that Angular rendered, place the child selector in the parent template and query it with @ViewChild(NotifyComponent). The resulting property refers to Angular's rendered child instance.

A second issue in the original code is that instance members must be accessed through this inside class methods: this.notify, not notify.

Think of Angular as a theater manager.

• Adding <notify></notify> to a template asks the manager to create an actor, put the actor on stage, and keep the stage display synchronized with the actor's state.
• Calling new NotifyComponent() creates a separate actor backstage. That actor can speak (console.log) and change clothes (test = 'Me'), but the audience cannot see them.
• @ViewChild gives the parent a reference to the actor Angular placed on stage.

Import ViewChild, render the child in the parent template, and declare a query for the child type.

import { Component, ViewChild } from '@angular/core';
import { NotifyComponent } from './notify.component';

@Component({
  selector: 'my-app',
  template: `
    <button (click)="submit()">Call Child Component Method</button>
    <notify></notify>
  `
})
export class AppComponent {
  @ViewChild(NotifyComponent) notify!: NotifyComponent;

  submit(): void {
    this.notify.callMethod();
  }
}

The child can remain simple:

import { Component } from '@angular/core';

@Component({
  selector: 'notify',
  template: '<h3>Notify {{ test }}</h3>'
})
   {
  test = ;

  ():  {
    .();
    . = ;
  }
}

Use this parent template:

<button (click)="submit()">Call Child Component Method</button>
<notify></notify>

Execution flow:

1. Angular creates AppComponent.
2. Angular reads its template and sees <notify>.
3. Angular creates a NotifyComponent instance, renders <h3>Notify {{ test }}</h3>, and assigns that instance to notify through @ViewChild.
4. The user clicks the button, so Angular calls submit().
5. submit() runs this.notify.callMethod() on the rendered child instance.
6. callMethod() assigns 'Me' to the child's test property.
7. Angular change detection updates interpolation, so the page displays Notify Me.

Calling a child method is useful when the parent owns an action and the child owns a focused UI behavior:

• A parent form page tells a custom input component to focus itself.
• A checkout page asks a payment widget to validate its current fields.
• A dashboard tells a chart component to refresh or reset its zoom.
• A dialog host calls open() or close() on a reusable modal component.
• A parent wizard tells the currently displayed step to save or validate.

Use this pattern for imperative UI actions. For ordinary data flow, prefer passing values to children with @Input() and receiving events with @Output().

In production Angular code, direct child method calls are usually kept narrow and intentional.

Guard against a missing conditional child

If the child is created with *ngIf or another conditional template block, it may not exist. Make the query optional and check it.

@ViewChild(NotifyComponent) notify?: NotifyComponent;

submit(): void {
  this.notify?.callMethod();
}

Prefer inputs for state

If the parent simply wants the child to display a value, bind the value rather than exposing a setter-like method.

// Parent template
<notify [message]="notificationMessage"></notify>

// Child
import { Component, Input } from '@angular/core';

@Component({
  selector: 'notify',
  template: '<h3>Notify {{ message }}</h3>'
})
export class NotifyComponent {
  () message = ;
}

Creating a component with new

// Incorrect for a rendered Angular component
this.notify = new NotifyComponent();

This creates an unmanaged class instance. It is not the <notify> instance in the DOM. Let Angular create components through the template, then use @ViewChild to obtain its reference.

Forgetting to render the child

@Component({
  template: '<button (click)="submit()">Run</button>'
})

Without <notify></notify>, there is no child in the parent's view for @ViewChild to find.

Omitting this

submit(): void {
  notify.callMethod(); // Incorrect: no local variable named notify
}

Use the class property:

..();

import { Component, ViewChild } from '@angular/core';
import { ChildComponent } from './child.component';

@Component({
  template: `
    <button (click)="run()">Run</button>
    <app-child></app-child>
  `
})
export class ParentComponent {
  @ViewChild(ChildComponent) child!: ChildComponent;

  run(): void {
    this.child.someMethod();
  }
}

• Put the child selector in the parent template.
• Import ViewChild from @angular/core.
• Query the child using its component class: @ViewChild(ChildComponent).
• Access class fields with this.child.
• The query is available after the view is created; use ngAfterViewInit() for setup code.
• If the child may not render, use child?: ChildComponent and this.child?.someMethod().

Why does new ChildComponent() not update the Angular page?

It creates a separate plain TypeScript object. Angular did not render that object or connect it to change detection and a template.

Why is @ViewChild undefined in the constructor?

Angular has not created the component view and its children during construction. The reference is available after view creation, such as in ngAfterViewInit().

Should I use @ViewChild to pass text to a child component?

Usually no. Use an @Input() binding for text, configuration, and other state. Use @ViewChild for behavior-oriented methods like focus() or reset().

Can a parent access more than one child component?

Yes. Use @ViewChildren(ChildComponent) to receive a QueryList of matching child instances.

What if the child is inside *ngIf?

The child reference exists only while the conditional template renders it. Use an optional query and check for it before calling a method.

Does Angular update the template after a child method changes a property?

Yes, for normal Angular event handling such as a button click, Angular runs change detection and updates interpolation like .

• Component templates — Templates declare which components Angular should render.
• @ViewChild — Retrieves one child component, directive, or template element from a view.
• @ViewChildren — Retrieves multiple matching children.
• Angular component lifecycle hooks — ngAfterViewInit() is important when working with view queries.
• @Input — The preferred parent-to-child mechanism for data.
• @Output and EventEmitter — The standard way for children to notify parents about events.
• Interpolation — {{ test }} displays component state in a template.
• Angular change detection — Synchronizes component state changes with rendered views.