Sure, but what I mean is if the native NS emailing function "displaces" the normal AfterSubmit trigger on create, you can't do anything to change that other than submit a Support ticket and wait.
But if your workflow is a "once-and-through" meaning it fires on create/copy only and exits after finishing, then you may be missing a "second chance" to catch that record and finish the remaining actions. You may have to have a different version of the action you want to execute on AfterSubmit, f.ex one that runs on the BeforeLoad that comes after creation is finished in the UI, or in a separate workflow which only fires on schedule using a saved search list of records which have "tobeemailed" checked and haven't been through whatever you wanted your AfterSubmit trigger to do. These are just examples and it would depend on exactly what you're trying to do and other context you cut from your ask for length.