MT Custom Action fix

[sinehome]

Description

Add 'input' on Kellimni staging customs action file.

Checklist

• Corresponding issue has been opened
• New tests added
• Feature flags / configuration added

Other Related Issues

None

Verification steps

AFTER YOU MERGE

1. Cut a release tag using the GitHub workflow. Wait for it to complete and the notification to be posted in the #aselo-deploys Slack channel.
2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P