Stay organized with collections
Save and categorize content based on your preferences.
The Workflows connector defines the built-in
functions that can be used to access other Google Cloud products within a
workflow.
This page provides an overview of the individual connector.
There is no need to import or load connector libraries in a workflow—connectors
work out of the box when used in a call step.
Cloud Firestore API
Accesses the NoSQL document database built for automatic scaling, high performance, and ease of application development.
To learn more, see the Cloud Firestore API documentation.
The Firestore connector allows you to connect to the Firestore APIs from within
a workflow.
The Firestore connector only supports databases created in Native mode.
Operations will fail if used on a database in Datastore mode.
To learn more about the difference between the two,
see Choosing between Native mode and Datastore mode.
Exports a copy of all or a subset of documents from Google Cloud
Firestore to another storage system, such as Google Cloud Storage.
Recent updates to documents may not be reflected in the export. The
export occurs in the background and its progress can be monitored and
managed via the Operation resource that is created. The output of an
export may only be used once the associated operation is done. If an
export operation is cancelled before completion it may leave partial
data behind in Google Cloud Storage. For more details on export behavior
and output format, refer to:
https://cloud.google.com/firestore/docs/manage-data/export-import
Imports documents into Google Cloud Firestore. Existing documents with
the same name are overwritten. The import occurs in the background and
its progress can be monitored and managed via the Operation resource
that is created. If an ImportDocuments operation is cancelled, it is
possible that a subset of the data has already been imported to Cloud
Firestore.
Lists the field configuration and metadata for this database. Currently,
FirestoreAdmin.ListFields only supports listing fields that have been
explicitly overridden. To issue this query, call
FirestoreAdmin.ListFields with the filter set to
indexConfig.usesAncestorConfig:false .
Updates a field configuration. Currently, field updates apply only to
single field index configuration. However, calls to
FirestoreAdmin.UpdateField should provide a field mask to avoid changing
any configuration that the caller isn't aware of. The field mask should
be specified as: { paths: "index_config" }. This call returns a
google.longrunning.Operation which may be used to track the status of
the field update. The metadata for the operation will be the type
FieldOperationMetadata. To configure the default field settings for the
database, use the special Field with resource name:
projects/{project_id}/databases/{database_id}/collectionGroups/__default__/fields/*.
Creates a composite index. This returns a google.longrunning.Operation
which may be used to track the status of the creation. The metadata for
the operation will be the type IndexOperationMetadata.
Applies a batch of write operations. The BatchWrite method does not
apply the write operations atomically and can apply them out of order.
Method does not allow more than one write per document. Each write
succeeds or fails independently. See the BatchWriteResponse for the
success status of each write. If you require an atomically applied set
of writes, use Commit instead.
Partitions a query by returning partition cursors that can be used to
run the query in parallel. The returned partition cursors are split
points that can be used by RunQuery as starting/end points for the query
results.
Starts asynchronous cancellation on a long-running operation. The server
makes a best effort to cancel the operation, but success is not
guaranteed. If the server doesn't support this method, it returns
google.rpc.Code.UNIMPLEMENTED. Clients can use Operations.GetOperation
or other methods to check whether the cancellation succeeded or whether
the operation completed despite cancellation. On successful
cancellation, the operation is not deleted; instead, it becomes an
operation with an Operation.error value with a google.rpc.Status.code of
1, corresponding to Code.CANCELLED.
Deletes a long-running operation. This method indicates that the client
is no longer interested in the operation result. It does not cancel the
operation. If the server doesn't support this method, it returns
google.rpc.Code.UNIMPLEMENTED.
Gets the latest state of a long-running operation. Clients can use this
method to poll the operation result at intervals as recommended by the
API service.
Lists operations that match the specified filter in the request. If the
server doesn't support this method, it returns UNIMPLEMENTED. NOTE:
the name binding allows API services to override the binding to use
different resource name schemes, such as users/*/operations. To
override the binding, API services can add a binding such as
"/v1/{name=users/*}/operations" to their service configuration. For
backwards compatibility, the default name includes the operations
collection id, however overriding users must ensure the name binding is
the parent resource, without the operations collection id.
Exports a copy of all or a subset of documents from Google Cloud
Firestore to another storage system, such as Google Cloud Storage.
Recent updates to documents may not be reflected in the export. The
export occurs in the background and its progress can be monitored and
managed via the Operation resource that is created. The output of an
export may only be used once the associated operation is done. If an
export operation is cancelled before completion it may leave partial
data behind in Google Cloud Storage.
Imports documents into Google Cloud Firestore. Existing documents with
the same name are overwritten. The import occurs in the background and
its progress can be monitored and managed via the Operation resource
that is created. If an ImportDocuments operation is cancelled, it is
possible that a subset of the data has already been imported to Cloud
Firestore.
Applies a batch of write operations. The BatchWrite method does not
apply the write operations atomically and can apply them out of order.
Method does not allow more than one write per document. Each write
succeeds or fails independently. See the BatchWriteResponse for the
success status of each write. If you require an atomically applied set
of writes, use Commit instead.
Partitions a query by returning partition cursors that can be used to
run the query in parallel. The returned partition cursors are split
points that can be used by RunQuery as starting/end points for the query
results.
Creates the specified index. A newly created index's initial state is
CREATING. On completion of the returned google.longrunning.Operation,
the state will be READY. If the index already exists, the call will
return an ALREADY_EXISTS status. During creation, the process could
result in an error, in which case the index will move to the ERROR
state. The process can be recovered by fixing the data that caused the
error, removing the index with delete, then re-creating the index with
create. Indexes with a single field cannot be created.
Exports a copy of all or a subset of documents from Google Cloud
Firestore to another storage system, such as Google Cloud Storage.
Recent updates to documents may not be reflected in the export. The
export occurs in the background and its progress can be monitored and
managed via the Operation resource that is created. The output of an
export may only be used once the associated operation is done. If an
export operation is cancelled before completion it may leave partial
data behind in Google Cloud Storage.
Imports documents into Google Cloud Firestore. Existing documents with
the same name are overwritten. The import occurs in the background and
its progress can be monitored and managed via the Operation resource
that is created. If an ImportDocuments operation is cancelled, it is
possible that a subset of the data has already been imported to Cloud
Firestore.
Lists the field configuration and metadata for this database. Currently,
FirestoreAdmin.ListFields only supports listing fields that have been
explicitly overridden. To issue this query, call
FirestoreAdmin.ListFields with the filter set to
indexConfig.usesAncestorConfig:false.
Updates a field configuration. Currently, field updates apply only to
single field index configuration. However, calls to
FirestoreAdmin.UpdateField should provide a field mask to avoid changing
any configuration that the caller isn't aware of. The field mask should
be specified as: { paths: "index_config" }. This call returns a
google.longrunning.Operation which may be used to track the status of
the field update. The metadata for the operation will be the type
FieldOperationMetadata. To configure the default field settings for the
database, use the special Field with resource name:
projects/{project_id}/databases/{database_id}/collectionGroups/__default__/fields/*.
Creates a composite index. This returns a google.longrunning.Operation
which may be used to track the status of the creation. The metadata for
the operation will be the type IndexOperationMetadata.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-30 UTC."],[],[]]