Model with Foreign Key already done, sequelize - node.js

Question

I am new to the backend field, I have been looking for solutions on how to make the model of two related tables, One-To-Many relationship of an existing database, but each example confuses me more.
CREATE TABLE my_db.person (
id INTEGER NOT NULL PRIMARY KEY AUTO_INCREMENT,
name VARCHAR(255) NOT NULL
created_at DATETIME,
craeted_by INTEGER, -- account_id
);
CREATE TABLE my_db.account (
id INTEGER NOT NULL PRIMARY KEY AUTO_INCREMENT,
email VARCHAR(255) UNIQUE,
password VARCHAR(255),
person_id INTEGER NOT NULL,
role INT NOT NULL
);
This is the Foreign Key that I want to make, the same
ALTER TABLE my_db.account
ADD CONSTRAINT fk_account_person_id
FOREIGN KEY (person_id)
REFERENCES my_db.person (id);
ON DELETE CASCADE
ON UPDATE CASCADE;
I did this but it doesn't work
person.ts
import { DataTypes } from 'sequelize';
import { db } from '../../db/connection';
import { Account } from './account';
export const Person = db.define( 'person', {
id: {
type: DataTypes.INTEGER,
allowNull: false,
primaryKey: true,
autoIncrement: true
},
name: {
type: DataTypes.STRING,
allowNull: false
},
created_at: {
type: DataTypes.DATE,
allowNull: true
},
created_by : {
type: DataTypes.INTEGER,
allowNull: true
}
}, {
timestamps: false,
});
Person.hasMany( Account, {
foreignKey: 'person_id',
onDelete: 'cascade',
onUpdate: 'cascade'
}
account.ts
import { DataTypes } from 'sequelize';
import { db } from '../../db/connection';
import { Person } from './Person';
export const Account = db.define( 'account', {
id: {
type: DataTypes.INTEGER,
allowNull: false,
primaryKey: true,
autoIncrement: true
},
email: {
type: DataTypes.STRING,
allowNull: false,
unique: true
},
password: {
type: DataTypes.STRING,
allowNull: false
},
person_id: {
type: DataTypes.INTEGER,
allowNull: false
},
role: {
type: DataTypes.INTEGER,
allowNull: false
}
}, {
timestamps: false,
});
Account.belongsTo( Person, {
foreignKey: 'person_id',
onDelete: 'CASCADE',
onUpdate: 'CASCADE'
}
Official Documentation
I thought of using the example from the documentation, however, it changes the name to the FK, but it does not show the exact table
enter image description here
enter image description here
clubId or TeamId?
enter image description here
In case the name of the attribute is not needed, does it infer it?
What if I have more than one FK to the same table? How would you infer those two without a constraint?
I did this, but I don't know where to put the constraint, since it already exists.
The database is in production, I cannot make changes to it, and I do not want a new constraint to be created