# Custom Integrations | Sentry for Cloud Functions for Firebase

In addition to the integrations that come with the SDK, you can also write custom integrations.

Custom integration must conform to the [Integration interface](https://github.com/getsentry/sentry-javascript/blob/master/packages/core/src/types-hoist/integration.ts).

A custom integration can be created and added to the SDK as follows:

```javascript
function myAwesomeIntegration() {
  return {
    name: "MyAwesomeIntegration",
    setup(client) {
      // Do something when the SDK is initialized
      // The client that is being setup is passed to the hook
    },
  };
}

Sentry.init({
  // ...
  integrations: [myAwesomeIntegration()],
});
```

All hooks on an integration are optional. The only required field is the `name`. You can use one or multiple of the following hooks in a custom integration:

### [`setup`](https://docs.sentry.io/platforms/javascript/guides/firebase/configuration/integrations/custom.md#setup)

The `setup` hook is called when the SDK is initialized. It receives the client instance as an argument. You should use this if you want to run some code on initialization.

```javascript
const integration = {
  name: "MyAwesomeIntegration",
  setup(client) {
    setupCustomSentryListener(client);
  },
};
```

### [`processEvent`](https://docs.sentry.io/platforms/javascript/guides/firebase/configuration/integrations/custom.md#processevent)

This hook can be used to modify events before they are sent to Sentry. It receives the event as an argument and should return the modified event. The hook also receives a hint object that may hold additional event metadata, and the client that is sending the event. You can also return `null` to drop the event from being sent.

```javascript
const integration = {
  name: "MyAwesomeIntegration",
  processEvent(event, hint, client) {
    event.extra = {
      ...event.extra,
      myCustomTag: "value",
    };
    // Return the modified event,
    // or return `null` to drop the event
    return event;
  },
};
```

You can also return a promise that resolves with an event or `null`. However, this is not recommended and should be avoided wherever possible, because it can delay event sending.

### [`preprocessEvent`](https://docs.sentry.io/platforms/javascript/guides/firebase/configuration/integrations/custom.md#preprocessevent)

This hook is similar to `processEvent`, but it is called before the event is passed to any other `processEvent` hook. It can be used in places where the order of processing is important.

In most cases, you should just use `processEvent`. Only use `preprocessEvent` if you need to ensure that your hook is called before any other `processEvent` hook.

Similar to `processEvent`, this hooks receives the event, hint, and client as arguments. However, this hook does not allow to return a modified event or `null` to drop the event - instead, you can only mutate the passed in event in this hook:

```javascript
const integration = {
  name: "MyAwesomeIntegration",
  preprocessEvent(event, hint, client) {
    event.extra = {
      ...event.extra,
      myCustomTag: "value",
    };
    // Nothing to return, just mutate the event
  },
};
```

### [`setupOnce`](https://docs.sentry.io/platforms/javascript/guides/firebase/configuration/integrations/custom.md#setuponce)

This hook is similar to `setup`, but it is only run once, even if the SDK is re-initialized. It does not receive any arguments. You should probably not use this, but use `setup` instead. The only reason to use `setupOnce` is e.g. when you may be calling `Sentry.init()` multiple times and you want to ensure a certain piece of code is only run once.

```javascript
const integration = {
  name: "MyAwesomeIntegration",
  setupOnce() {
    wrapLibrary();
  },
};
```

### [`afterAllSetup`](https://docs.sentry.io/platforms/javascript/guides/firebase/configuration/integrations/custom.md#afterallsetup)

This hook is triggered after `setupOnce()` and `setup()` have been called for all integrations. You can use it if it is important that all other integrations have been run before.

In most cases, you should not need to use this hook, and should use `setup` instead.

The hook receives the `client` that is being set up as the first argument.

```javascript
const integration = {
  name: "MyAwesomeIntegration",
  afterAllSetup(client) {
    // We can be sure that all other integrations
    // have run their `setup` and `setupOnce` hooks now
    startSomeThing(client);
  },
};
```
