<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D54z00008U4pjtCABOkta Identity EngineWorkflowsAnswered2022-12-21T19:59:10.000Z2022-12-05T21:40:44.000Z2022-12-21T19:59:10.000Z

JacksonK.52224 (Customer) asked a question.

December 5, 2022 at 9:40 PM
Trying to set up Forwarding Emails but workflow is stating a 404 Error

Hi there,

 

I'm trying to setup a workflow in which when a user is going to be offboarded, we will add the user's name to a google sheet and that will include the offboarded user's email, the manager's email to forward emails and transfer files, and finally the IT associate's name that is responsible for the transfer.

 

For some reason the "Forward Emails" Okta app action produces a 404 error:

 

/help/servlet/rtaImage?refid=0EM4z000005J7yC

 

I was told that the "service account" would be the admin's email, is that the issue? What is the service account suppossed to be?

 

I have no issue in "Create Transfer Request" as that had done it correctly in a separate workflow:

 

/help/servlet/rtaImage?refid=0EM4z000005J7yl

 

Anyone have any tips?

  • 7 answers
  • 683 views

  • TimL.58332 (Workflows)

    @JacksonK.52224 (Customer)​ 

     

    Sorry I didn't see this most recent reply. I do not believe any of our "Built-in" actions on the card can perform this task. You would need to determine "If" this change can be accomplished via a public Google REST API call.

     

    If the API is part of the /gmail or /directory you could likely leverage a Custom API Action (gmail or workspace) to access the endpoint using your existing configured credentials. If it isn't one of the those the complexity goes way up.

     

    Relative url for Custom API Actions assume the following:

     

    https://gmail.googleapis.com/gmail/

     

    So for the following url the "Bold" would be the relative portion that needs to be defined for the endpoint (note: this is just a random example and likely not the API you need)

     

    https://gmail.googleapis.com/gmail/v1/users/{userId}/settings/autoForwarding

    For Workspace its:

     

    https://admin.googleapis.com/admin/directory/v1/customer/customer_id/roles/ALL/privileges

     

    Expand Post
    Selected as Best

  • TimL.58332 (Workflows)

    @JacksonK.52224 (Customer)​ 

     

    Typically people leverage the dynamic drop down to select the service account. But if you want it to be a variable value (such as you have selected) for the input you need to specify the GCP service account IAM > service account.

     

    They are typically formatted similar to:

     

    first-last@projectName.iam.gserviceaccount.com

    Expand Post

    • JacksonK.52224 (Customer)

      So what I figured out is that I actually don't have a Google Cloud Platform account, so it's just not finding a service account. I'm not even familiar with that service. But if I create one with Google, is there a limit on how many email forwards can be initiated and saved?

  • TimL.58332 (Workflows)

    @JacksonK.52224 (Customer)​  I really don't know the answer on the Google side of things. Typically forward emails is going to be "Many to One" so like X-Employee's being forwarded to some specific location. The forward is going to be on the X-Employee's account not on the destination.

     

    As far as GCP is concerned it is required for quite a few API actions in the Workspace Suite. You would need to refer to Googles documentation though.

    Expand Post

    • JacksonK.52224 (Customer)

      Gotcha, I've setup GCP and the forwarding works... however not the way we want.

       

      I was wondering if there was a gmail "default routing" option instead? We generally suspend gmail accounts when they are offboarded. The gmail forwarding that Okta has in it's workflow only enables forwarding, so when the account is suspended, the forwarding stops.

       

      When we add a forwarding address we use, in google admin, default routing. The emails get forwarded regardless if the user is active or suspended:

       

      imageDoes Okta have that option somewhere?

      Expand Post

      • TimL.58332 (Workflows)

        @JacksonK.52224 (Customer)​ 

         

        Sorry I didn't see this most recent reply. I do not believe any of our "Built-in" actions on the card can perform this task. You would need to determine "If" this change can be accomplished via a public Google REST API call.

         

        If the API is part of the /gmail or /directory you could likely leverage a Custom API Action (gmail or workspace) to access the endpoint using your existing configured credentials. If it isn't one of the those the complexity goes way up.

         

        Relative url for Custom API Actions assume the following:

         

        https://gmail.googleapis.com/gmail/

         

        So for the following url the "Bold" would be the relative portion that needs to be defined for the endpoint (note: this is just a random example and likely not the API you need)

         

        https://gmail.googleapis.com/gmail/v1/users/{userId}/settings/autoForwarding

        For Workspace its:

         

        https://admin.googleapis.com/admin/directory/v1/customer/customer_id/roles/ALL/privileges

         

        Expand Post
        Selected as Best

      • JacksonK.52224 (Customer)

        Gotcha, thanks. I'll look into it, might be more trouble than it's worth.

  • TimL.58332 (Workflows)

    @JacksonK.52224 (Customer)​  - Workflows is just a tool using the API's that are available from the vendor. We don't have options available that they do not have available.

     

    The Forward Emails action on the Gmail card performs their Forward Emails API action which sets the Settings > See All Settings > Forwarding and POP/IMAP > Forwarding in their GMail client.

     

    If you are attempting to perform an action in Google and you can figure out a method to meet your needs through their UI/UX you would then need to refer to their documentation to determine which API endpoint (if exists) can perform the same action.

     

    Once that is determined it is likely possible to automate it with Workflows.

    Expand Post
This question is closed.
Loading
Trying to set up Forwarding Emails but workflow is stating a 404 Error