Skip to Content

Google Drive Create File activity

Introduction

A Google Drive Create File activity, using its Google Drive connection, creates files in Google Drive and is intended to be used as a target to consume data in an operation.

Create a Google Drive Create File activity

An instance of a Google Drive Create File activity is created from a Google Drive connection using its Create File activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Create an activity instance in Component reuse.

An existing Google Drive Create File activity can be edited from these locations:

Configure a Google Drive Create File activity

Follow these steps to configure a Google Drive Create File activity:

Step 1: Enter a name

In this step, enter a name for the activity. Each user interface element of this step is described below.

Google Drive Create File activity configuration step 1

  • Name: Enter a name to identify the activity. The name must be unique for each Google Drive Create File activity and must not contain forward slashes / or colons :.

  • Support all drives: Select to access shared drives when using this activity. If unselected, only My Drive will be accessible.

  • Optional Settings: Click to expand additional optional settings:

    • Content Type: Use the menu to specify the MIME type being created. If a MIME type is not specified, the Google Drive API v3 attempts to detect and automatically set the MIME type. If the MIME type can't be detected, it is set to application/octet-stream.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

Google Drive Create File activity configuration step 2

  • Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    The Google Drive connector uses the Google Drive API v3. Refer to the API documentation for information on the schema nodes and fields.

  • Refresh: Click the refresh icon Refresh icon or the word Refresh to regenerate schemas from the Google Drive endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring a Google Drive Create File activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

Google Drive Create File activities can be used as a target with these operation patterns:

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.